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

Re: Forward-port a patch using git

From
Jeff King <peff@peff.net>
Date
Dec 1, 2010, 18:16 UTC
Message-ID
<20101201181626.GD7774@sigill.intra.peff.net>
In-Reply-To
<4CF68FCB.2030301@shiftmail.org>
On Wed, Dec 01, 2010 at 07:11:23PM +0100, Spelic wrote:
Show 5 quoted lines
> 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:

Show 7 quoted lines
> 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
Previous: Spelic
Message 3 of 3 in “Forward-port a patch using git”
  1. SpelicDec 1, 2010
  2. SpelicDec 1, 2010
  3. Jeff KingDec 1, 2010

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.