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

Re: [PATCH 4/5] Documentation: document AUTO_MERGE

From
Elijah Newren <newren@gmail.com>
Date
Apr 15, 2023, 23:31 UTC
Message-ID
<CABPp-BGtewvrsO_9hf5A4iqpTBW7VL1p8skwMGA+tFju1emQ4w@mail.gmail.com>
In-Reply-To
<5cd89e46-f099-24bb-ebe4-fabdd6f94aef@gmail.com>

On Sat, Apr 15, 2023 at 8:36 AM Philippe Blain <levraiphilippeblain@gmail.com> wrote:

>
> Hi Elijah,
>
<snip>
Show 7 quoted lines
> > (By contrast, the closely related --remerge-diff option to `git log`
> > or `git show` does help see the resolution of *both* the textual and
> > non-textual conflicts, but of course one can't use that option on the
> > current merge until after first commiting the existing changes.)
>
> That's true. And, remerge-diff only helps when actually looking at two-way
> merge commit, not with conflicts hit during a rebase, cherry-pick or revert.

Good point. I have a small patchset to create an option allowing folks to see how conflicts were resolved in reverts, and in cherry-picks made with the -x option. I made it over two years ago, but never ended up deciding whether to submit it or not. At some point I put it up on gitgitgadget, at https://github.com/gitgitgadget/git/pull/1151.

Points against it are that it doesn't work for rebases (because we don't know which commits they were taken from) or for many cherry-picks. Given the lower utility, and the fact that it involves commit message scraping (looking for "reverts commit <X>" and "(cherry-picked from <X>)"), I never ended up pushing for it.

> A semi-related trick I use to check conflict resolution during a rebase (after
> resolving the conflicts but before 'git rebase --continue') is to manually
> construct a commit from the index and use 'git range-diff' to compare it
> to REBASE_HEAD.
Heh, I have a semi-related trick as well.  During rebases, when I want
to compare overall diffs for the current commit against what it was
picked from, I tend to use:
   mydiff <(git log -1 -p REBASE_HEAD) <(git diff HEAD)
where `mydiff` is a specialized wrapper around `git diff --no-index`
that actually reads the contents of /dev/fd/<value> instead of
treating it as a symlink.  (Though if I don't have that script handy,
I just plug in `diff -u` for `mydiff`).
Previous: Philippe BlainNext: Junio C Hamano
Message 21 of 35 in “Document 'AUTO_MERGE' and more special refs”
  1. 0/5 Document 'AUTO_MERGE' and more special refsPhilippe Blain via GitGitGadget, Apr 14, 2023
  2. 1/5 revisions.txt: document more special refsPhilippe Blain via GitGitGadget, Apr 14, 2023
  3. Junio C HamanoApr 14, 2023
  4. Felipe ContrerasApr 15, 2023
  5. Victoria DyeApr 14, 2023
  6. Taylor BlauApr 14, 2023
  7. Felipe ContrerasApr 15, 2023
  8. 3/5 git-merge.txt: modernize word choice in "True merge" sectionPhilippe Blain via GitGitGadget, Apr 14, 2023
  9. Junio C HamanoApr 14, 2023
  10. 2/5 completion: complete REVERT_HEAD and BISECT_HEADPhilippe Blain via GitGitGadget, Apr 14, 2023
  11. Junio C HamanoApr 14, 2023
  12. 5/5 completion: complete AUTO_MERGEPhilippe Blain via GitGitGadget, Apr 14, 2023
  13. 4/5 Documentation: document AUTO_MERGEPhilippe Blain via GitGitGadget, Apr 14, 2023
  14. Taylor BlauApr 14, 2023
  15. Eric SunshineApr 15, 2023
  16. Elijah NewrenApr 15, 2023
  17. Eric SunshineApr 15, 2023
  18. Elijah NewrenApr 16, 2023
  19. Elijah NewrenApr 15, 2023
  20. Philippe BlainApr 15, 2023
  21. Elijah NewrenApr 15, 2023
  22. Junio C HamanoApr 14, 2023
  23. Victoria DyeApr 14, 2023
  24. Elijah NewrenApr 15, 2023
  25. Chris TorekApr 16, 2023
  26. 0/6 Document 'AUTO_MERGE' and more special refsPhilippe Blain via GitGitGadget, May 22, 2023
  27. 1/6 revisions.txt: use description list for special refsPhilippe Blain via GitGitGadget, May 22, 2023
  28. 2/6 revisions.txt: document more special refsPhilippe Blain via GitGitGadget, May 22, 2023
  29. 4/6 git-merge.txt: modernize word choice in "True merge" sectionPhilippe Blain via GitGitGadget, May 22, 2023
  30. 3/6 completion: complete REVERT_HEAD and BISECT_HEADPhilippe Blain via GitGitGadget, May 22, 2023
  31. 5/6 Documentation: document AUTO_MERGEPhilippe Blain via GitGitGadget, May 22, 2023
  32. 6/6 completion: complete AUTO_MERGEPhilippe Blain via GitGitGadget, May 22, 2023
  33. Elijah NewrenJun 1, 2023
  34. Junio C HamanoJun 1, 2023
  35. Junio C HamanoJun 1, 2023

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.