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

Re: SEGV in git-merge recursive:

From
Alex Riesen <raa.lkml@gmail.com>
Date
Mar 29, 2007, 15:04 UTC
Message-ID
<81b0412b0703290804n13af6f40we79f7251562c540@mail.gmail.com>
In-Reply-To
<81b0412b0703290744h34b6ef01s4e6f90b1d7ed231b@mail.gmail.com>
On 3/29/07, Alex Riesen <raa.lkml@gmail.com> wrote:
Show 17 quoted lines
> > Here is the output from that more verbose version:
> >
> > Merging HEAD with 0134d595adb023841750f1ce84ecb94dd4e4c9cb
> > Merging:
> > 922ee6e3f1222c8e171e6ea0b6ac0f28fb1f0683 Mail.
> > 0134d595adb023841750f1ce84ecb94dd4e4c9cb Mail.
> > found 2 common ancestor(s):
> > 29e722de58df3cd82600fa5215ec26f80a8c0f9a Mail.
> > 2c3490d82610d12d8dfde36b29c4ec5a50955b89 Mail.
> >   Merging:
> >   29e722de58df3cd82600fa5215ec26f80a8c0f9a Mail.
> >   2c3490d82610d12d8dfde36b29c4ec5a50955b89 Mail.
> >   found 1 common ancestor(s):
> >   e2123cfd9a53e441c7c715627953606c6093e0e4 Merge commit 'origin'
> >   CONFLICT (rename/rename): Rename .drafts/new/1175001142.P509Q1.hermes->.mom/cur/1175098106.P18146Q0M209985.socrates:2,S in branch Temporary merge branch 1 rename .drafts/new/1175001142.P509Q1.hermes->.drafts/cur/1175001142.P509Q1.hermes:2, in Temporary merge branch 2
>
> Rename conflict... Will see, if I can reproduce it without your repo.

I failed to reproduce it. My attempt attached (that's for your reference pleasure, Dscho). The output was:

GIT_MERGE_VERBOSITY=99 git merge B
Merging HEAD with B
Merging:
18d0538 rename
d4badb1 rename
found 2 common ancestor(s):
962b369 change
9cc8ebd change
  Merging:
  962b369 change
  9cc8ebd change
  found 1 common ancestor(s):
  a46f64f init
CONFLICT (rename/rename): Rename 1->a in branch HEAD rename 1->b in B
Automatic merge failed; fix conflicts and then commit the result.

Tom, either the stack trace of -O0 -ggdb or your repo is badly needed. The stack preferred, as I have that feeling it'll just work everywhere else but your system (can you try it somewhere else, BTW?).

Previous: Tom PrinceNext: Alex Riesen
Message 11 of 31 in “SEGV in git-merge recursive:”
  1. Tom PrinceMar 29, 2007
  2. Alex RiesenMar 29, 2007
  3. Tom PrinceMar 29, 2007
  4. Alex RiesenMar 29, 2007
  5. Tom PrinceMar 29, 2007
  6. Alex RiesenMar 29, 2007
  7. Tom PrinceMar 29, 2007
  8. Alex RiesenMar 29, 2007
  9. Alex RiesenMar 29, 2007
  10. Tom PrinceMar 29, 2007
  11. Alex RiesenMar 29, 2007
  12. Alex RiesenMar 29, 2007
  13. Alex RiesenMar 29, 2007
  14. An attempt to resolve a rename/rename conflict in recursive mergeAlex Riesen, Mar 29, 2007
  15. Alex RiesenMar 29, 2007
  16. Linus TorvaldsMar 29, 2007
  17. Linus TorvaldsMar 29, 2007
  18. Alex RiesenMar 29, 2007
  19. Johannes SchindelinMar 30, 2007
  20. Linus TorvaldsMar 31, 2007
  21. Linus TorvaldsMar 31, 2007
  22. Alex RiesenMar 31, 2007
  23. Keep rename/rename conflicts of intermediate merges while doing recursive mergeAlex Riesen, Mar 31, 2007
  24. Jakub NarebskiMar 31, 2007
  25. Johannes SchindelinMar 31, 2007
  26. Johannes SchindelinMar 31, 2007
  27. Linus TorvaldsMar 31, 2007
  28. Alex RiesenMar 31, 2007
  29. Junio C HamanoMar 31, 2007
  30. Johannes SchindelinMar 31, 2007
  31. Tom PrinceMar 29, 2007

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.