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

Re: Effective difference between git-rebase and git-resolve

From
MSMarc Singer <elf@buici.com>
Date
Mar 25, 2006, 06:32 UTC
Message-ID
<20060325063225.GA13791@buici.com>
In-Reply-To
<7v64m3ys3a.fsf@assigned-by-dhcp.cox.net>
On Fri, Mar 24, 2006 at 10:08:09PM -0800, Junio C Hamano wrote:
Show 13 quoted lines
> > Junio, is there some magic to restart a rebase after you've fixed up the 
> > conflicts?
> 
> The modern rebase is essentially git-format-patch piped to
> git-am (with -3 flag to allow falling back to three-way merge),
> and all the familiar "the patch did not apply -- what now?"
> techniques can be employed.
> 
> Since the pre-image blobs recorded in the intermediate
> format-patch output by definition exist in your repository, it
> always falls back to three-way merge when the patch does not
> apply cleanly.  Then you can resolve and say "git am --resolved"
> to continue.

By modern do you mean newer than 1.2.4? I comprehend what you're layin' down here, but I don't know if I need to do something different.

Moreover, it isn't clear to me if git-rebase is better than git-merge.
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 10 in “Effective difference between git-rebase and git-resolve”
  1. Marc SingerMar 25, 2006
  2. Linus TorvaldsMar 25, 2006
  3. Junio C HamanoMar 25, 2006
  4. Marc SingerMar 25, 2006
  5. Junio C HamanoMar 25, 2006
  6. J. Bruce FieldsMar 26, 2006
  7. Junio C HamanoMar 25, 2006
  8. Johannes SchindelinMar 25, 2006
  9. Mark WoodingMar 25, 2006
  10. Johannes SchindelinMar 25, 2006

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.