From: Jeff King <peff@peff.net>
To: Spelic <spelic@shiftmail.org>
Cc: git@vger.kernel.org
Subject: Re: Forward-port a patch using git
Date: Wed, 1 Dec 2010 13:16:26 -0500 [thread overview]
Message-ID: <20101201181626.GD7774@sigill.intra.peff.net> (raw)
In-Reply-To: <4CF68FCB.2030301@shiftmail.org>
On Wed, Dec 01, 2010 at 07:11:23PM +0100, Spelic wrote:
> I found it myself, sorry for having asked.
>
> It was:
>
> checkout v2.6.36
Be aware that checking out the v2.6.36 tag will mean you are not on any
branch. So this will work fine:
> apply 1 patch
> commit
> apply 1 patch
> commit
> ...
> rebase v2.6.37-rc4
> git format-patch -o <destdir> -numpatches
But at the end, you will not have any branch tip pointing to your
rebased work. If all you want are the patches as output, then that's
fine. But you may want to do:
git checkout -b some-useful-name v2.6.36
as the first step instead, which means you can come back to your rebased
work later as "some-useful-name".
-Peff
prev parent reply other threads:[~2010-12-01 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 15:37 Forward-port a patch using git Spelic
2010-12-01 18:11 ` Spelic
2010-12-01 18:16 ` Jeff King [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=20101201181626.GD7774@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=spelic@shiftmail.org \
/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).