{"thread":{"id":"17620","subject":"RPM to GIT tree integration?","startedAt":"2009-02-06T17:05:49Z","lastAt":"2009-02-07T05:57:47Z","messageCount":3,"participants":["Alex Bennee","Daniel Barkalow","James Davidson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"103532","messageId":"b2cdc9f30902060905mb605a93oe8f9cc5795f3e008@mail.gmail.com","threadId":"17620","inReplyTo":null,"subject":"RPM to GIT tree integration?","fromName":"Alex Bennee","fromEmail":"kernel-hacker@bennee.com","sentAt":"2009-02-06T17:05:49Z","receivedAt":"2009-02-06T17:05:49Z","isPatch":false,"sender":{"key":"kernel-hacker@bennee.com","avatar":null},"body":"Hi,\n\nThis is a wild shot in the dark but I thought I'd better ask in case\nsome one has. Has anyone created a script/tool that can take a src RPM and\napply it's patches (in sequence) to an existing GIT tree?\n\nIn my case I just want a GIT tree for a vendor kernel. I could just\nprep an SRC RPM and commit the thing wholesale into GIT and start\nhacking but then I'd loose all the history benefits.\n\n-- \nAlex, homepage: http://www.bennee.com/~alex/\nCV: http://www.bennee.com/~alex/cv.php\n"},{"id":"103537","messageId":"alpine.LNX.1.00.0902061318310.19665@iabervon.org","threadId":"17620","inReplyTo":"b2cdc9f30902060905mb605a93oe8f9cc5795f3e008@mail.gmail.com","subject":"Re: RPM to GIT tree integration?","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2009-02-06T18:29:17Z","receivedAt":"2009-02-06T18:29:17Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Fri, 6 Feb 2009, Alex Bennee wrote:\n\n> Hi,\n> \n> This is a wild shot in the dark but I thought I'd better ask in case\n> some one has. Has anyone created a script/tool that can take a src RPM and\n> apply it's patches (in sequence) to an existing GIT tree?\n\nI haven't heard of one, but it would probably be easy to do with \ngit-fast-import; you could take a look at \ncontrib/fast-import/import-tars.perl.\n\n> In my case I just want a GIT tree for a vendor kernel. I could just\n> prep an SRC RPM and commit the thing wholesale into GIT and start\n> hacking but then I'd loose all the history benefits.\n\nI think the biggest benefit would actually be identifying the upstream \nkernel that has the patches applied to it, which takes a certain amount of \ninspection and familiarity with Linus's kernel repository, but not really \na tool.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"103597","messageId":"20090207055747.GA5788@greycastle.net","threadId":"17620","inReplyTo":"b2cdc9f30902060905mb605a93oe8f9cc5795f3e008@mail.gmail.com","subject":"Re: RPM to GIT tree integration?","fromName":"James Davidson","fromEmail":"james@greycastle.net","sentAt":"2009-02-07T05:57:47Z","receivedAt":"2009-02-07T05:57:47Z","isPatch":false,"sender":{"key":"james@greycastle.net","avatar":null},"body":"On Fri Feb 06, 2009 at 05:05:49PM +0000, Alex Bennee <kernel-hacker@bennee.com> wrote:\n> This is a wild shot in the dark but I thought I'd better ask in case\n> some one has. Has anyone created a script/tool that can take a src RPM and\n> apply it's patches (in sequence) to an existing GIT tree?\n\nThis may be what you are looking for:\nhttp://www.gnome.org/~federico/news-2008-07.html#rpm2git\n\n> In my case I just want a GIT tree for a vendor kernel. I could just\n> prep an SRC RPM and commit the thing wholesale into GIT and start\n> hacking but then I'd loose all the history benefits.\n\nThere is also a \"How to use rpm2git\" screencast:\nhttp://blip.tv/file/1155469\n\n-- \nJames Davidson                     (o_   \njames@greycastle.net               //\\\nhttp://moria.greycastle.net/       V_/_\n"}]}