From: James Davidson <james@greycastle.net>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: RPM to GIT tree integration?
Date: Fri, 6 Feb 2009 21:57:47 -0800 [thread overview]
Message-ID: <20090207055747.GA5788@greycastle.net> (raw)
In-Reply-To: <b2cdc9f30902060905mb605a93oe8f9cc5795f3e008@mail.gmail.com>
On Fri Feb 06, 2009 at 05:05:49PM +0000, Alex Bennee <kernel-hacker@bennee.com> wrote:
> 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?
This may be what you are looking for:
http://www.gnome.org/~federico/news-2008-07.html#rpm2git
> 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.
There is also a "How to use rpm2git" screencast:
http://blip.tv/file/1155469
--
James Davidson (o_
james@greycastle.net //\
http://moria.greycastle.net/ V_/_
prev parent reply other threads:[~2009-02-07 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 17:05 RPM to GIT tree integration? Alex Bennee
2009-02-06 18:29 ` Daniel Barkalow
2009-02-07 5:57 ` James Davidson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090207055747.GA5788@greycastle.net \
--to=james@greycastle.net \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).