git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RPM to GIT tree integration?

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Feb 6, 2009, 18:29 UTC
Message-ID
<alpine.LNX.1.00.0902061318310.19665@iabervon.org>
In-Reply-To
<b2cdc9f30902060905mb605a93oe8f9cc5795f3e008@mail.gmail.com>
On Fri, 6 Feb 2009, Alex Bennee wrote:
Show 5 quoted lines
> Hi,
> 
> This is a wild shot in the dark but I thought I'd better ask in case
> some one has. Has anyone created a script/tool that can take a src RPM and
> apply it's patches (in sequence) to an existing GIT tree?

I haven't heard of one, but it would probably be easy to do with git-fast-import; you could take a look at contrib/fast-import/import-tars.perl.

> In my case I just want a GIT tree for a vendor kernel. I could just
> prep an SRC RPM and commit the thing wholesale into GIT and start
> hacking but then I'd loose all the history benefits.

I think the biggest benefit would actually be identifying the upstream kernel that has the patches applied to it, which takes a certain amount of inspection and familiarity with Linus's kernel repository, but not really a tool.

	-Daniel
*This .sig left intentionally blank*
Previous: Alex BenneeNext: James Davidson
Message 2 of 3 in “RPM to GIT tree integration?”
  1. Alex BenneeFeb 6, 2009
  2. Daniel BarkalowFeb 6, 2009
  3. James DavidsonFeb 7, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.