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

Re: git rebase to move a batch of patches onto the current branch

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jul 24, 2008, 20:30 UTC
Message-ID
<20080724203049.GC3760@blimp.local>
In-Reply-To
<32541b130807241316x4f85bcdfw12857be575fb3289@mail.gmail.com>
Avery Pennarun, Thu, Jul 24, 2008 22:16:06 +0200:
Show 9 quoted lines
> On 7/24/08, Alex Riesen <raa.lkml@gmail.com> wrote:
> >     gcp3 ()
> >     {
> >         git format-patch -k --stdout --full-index "$@" | git am -k -3 --binary
> >     }
> 
> But that'll give up when there are conflicts, right?  git-rebase lets
> me fix them in a nice way.
> 

No, it same as in rebase. You'll fix them and do "git am --resolved". See manpage of git am.

Previous: Avery PennarunNext: Avery Pennarun
Message 4 of 9 in “git rebase to move a batch of patches onto the current branch”
  1. Avery PennarunJul 24, 2008
  2. Alex RiesenJul 24, 2008
  3. Avery PennarunJul 24, 2008
  4. Alex RiesenJul 24, 2008
  5. Avery PennarunJul 24, 2008
  6. Daniel BarkalowJul 25, 2008
  7. Stephan BeyerJul 25, 2008
  8. Alex RiesenJul 25, 2008
  9. Björn SteinbrinkJul 25, 2008

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.