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

Re: [PATCH 2/3] revision: add "--ignore-merges" option to counteract "-m"

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 28, 2020, 21:01 UTC
Message-ID
<xmqqv9i7cq1k.fsf@gitster.c.googlers.com>
In-Reply-To
<20200728163853.GB2650252@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 46 quoted lines
> The "-m" option sets revs->ignore_merges to "0", but there's no way to
> undo it. This probably isn't something anybody overly cares about, since
> "1" is already the default, but it will serve as an escape hatch when we
> flip the default for ignore_merges to "0" in more situations.
>
> We'll also add a few extra niceties:
>
>   - initialize the value to "-1" to indicate "not set", and then resolve
>     it to the normal 0/1 bool in setup_revisions(). This lets any tweak
>     functions, as well as setup_revisions() itself, avoid clobbering the
>     user's preference (which until now they couldn't actually express).
>
>   - since we now have --ignore-merges, let's add the matching
>     --no-ignore-merges, which is just a synonym for "-m". In fact, it's
>     simpler to just document --no-ignore-merges alongside "-m", and
>     leave it implied that its opposite countermands it.
>
> The new test shows that this behaves just the same as the current
> behavior without "-m".
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> I pulled the option name from the rev_info field name. It might be too
> broad (we are not ignoring merges during the traversal, only for the
> diff). It could be "--no-diff-merges" or something, but that would
> involve flipping the sense of the boolean (but that would just be in the
> code, not user-visible, so not that big a deal).
>
>  Documentation/rev-list-options.txt            |  1 +
>  builtin/log.c                                 |  4 +-
>  revision.c                                    | 10 ++-
>  revision.h                                    |  2 +-
>  t/t4013-diff-various.sh                       |  1 +
>  ...g_--ignore-merges_-p_--first-parent_master | 78 +++++++++++++++++++
>  6 files changed, 90 insertions(+), 6 deletions(-)
>  create mode 100644 t/t4013/diff.log_--ignore-merges_-p_--first-parent_master
>
> diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
> index b01b2b6773..fbd8fa0381 100644
> --- a/Documentation/rev-list-options.txt
> +++ b/Documentation/rev-list-options.txt
> @@ -1148,6 +1148,7 @@ options may be given. See linkgit:git-diff-files[1] for more options.
>  	rename or copy detection have been requested).
>  
>  -m::
> +--no-ignore-merges::

This invites a natural "does --ignore-merges exist, and if so what does it do?" Why not to have "--[no-]ignore-merges" as a separate entry immediately after the existing "-m" instead?

>  	This flag makes the merge commits show the full diff like
>  	regular commits; for each merge parent, a separate log entry
>  	and diff is generated. An exception is that only diff against
That is,
	--[no-]ignore-merges::
		`--no-ignore-merges` is a synonym to `-m`.
		`--ignore-merges` countermands an earlier `-m` that
		is either explicitly or implicitly given.
or something along the line, perhaps?
Show 9 quoted lines
> diff --git a/t/t4013-diff-various.sh b/t/t4013-diff-various.sh
> index 43267d6024..8f9181316f 100755
> --- a/t/t4013-diff-various.sh
> +++ b/t/t4013-diff-various.sh
> @@ -297,6 +297,7 @@ log --root --patch-with-stat --summary master
>  log --root -c --patch-with-stat --summary master
>  # improved by Timo's patch
>  log --root --cc --patch-with-stat --summary master
> +log --ignore-merges -p --first-parent master
This explicitly says "I do not want to see diff for merges" ...
Show 16 quoted lines
>  log -p --first-parent master
>  log -m -p --first-parent master
>  log -m -p master
> diff --git a/t/t4013/diff.log_--ignore-merges_-p_--first-parent_master b/t/t4013/diff.log_--ignore-merges_-p_--first-parent_master
> new file mode 100644
> index 0000000000..fa0cdc8a23
> --- /dev/null
> +++ b/t/t4013/diff.log_--ignore-merges_-p_--first-parent_master
> @@ -0,0 +1,78 @@
> +$ git log --ignore-merges -p --first-parent master
> +commit 59d314ad6f356dd08601a4cd5e530381da3e3c64
> +Merge: 9a6d494 c7a2ab9
> +Author: A U Thor <author@example.com>
> +Date:   Mon Jun 26 00:04:00 2006 +0000
> +
> +    Merge branch 'side' into master
... and that is honored here?  Good.
Previous: Jeff KingNext: Jeff King
Message 6 of 86 in “making --first-parent imply -m”
  1. 0/3 making --first-parent imply -mJeff King, Jul 28, 2020
  2. 1/3 log: drop "--cc implies -m" logicJeff King, Jul 28, 2020
  3. 2/3 revision: add "--ignore-merges" option to counteract "-m"Jeff King, Jul 28, 2020
  4. Chris TorekJul 28, 2020
  5. Jeff KingJul 29, 2020
  6. Junio C HamanoJul 28, 2020
  7. Jeff KingJul 29, 2020
  8. Jeff KingJul 29, 2020
  9. Junio C HamanoJul 29, 2020
  10. 3/3 log: enable "-m" automatically with "--first-parent"Jeff King, Jul 28, 2020
  11. Jeff KingJul 28, 2020
  12. Junio C HamanoJul 28, 2020
  13. Jeff KingJul 28, 2020
  14. Taylor BlauJul 28, 2020
  15. 0/7 making log --first-parent imply -mJeff King, Jul 29, 2020
  16. 1/7 log: drop "--cc implies -m" logicJeff King, Jul 29, 2020
  17. 2/7 revision: add "--no-diff-merges" option to counteract "-m"Jeff King, Jul 29, 2020
  18. 3/7 log: enable "-m" automatically with "--first-parent"Jeff King, Jul 29, 2020
  19. Junio C HamanoJul 29, 2020
  20. 4/7 doc/git-log: move "Diff Formatting" from rev-list-optionsJeff King, Jul 29, 2020
  21. Junio C HamanoJul 29, 2020
  22. Jeff KingJul 29, 2020
  23. 5/7 doc/git-log: drop "-r" diff optionJeff King, Jul 29, 2020
  24. 6/7 doc/git-log: move "-t" into diff-options listJeff King, Jul 29, 2020
  25. Junio C HamanoJul 29, 2020
  26. Jeff KingJul 29, 2020
  27. 7/7 doc/git-log: clarify handling of merge commit diffsJeff King, Jul 29, 2020
  28. Chris TorekJul 29, 2020
  29. Sergey OrganovJul 29, 2020
  30. Jeff KingJul 31, 2020
  31. Sergey OrganovAug 2, 2020
  32. Junio C HamanoAug 2, 2020
  33. Sergey OrganovAug 3, 2020
  34. Junio C HamanoAug 3, 2020
  35. Sergey OrganovAug 3, 2020
  36. Junio C HamanoAug 3, 2020
  37. Sergey OrganovAug 3, 2020
  38. Jeff KingAug 3, 2020
  39. Sergey OrganovAug 3, 2020
  40. Jeff KingAug 3, 2020
  41. Sergey OrganovAug 3, 2020
  42. Jeff KingAug 3, 2020
  43. Sergey OrganovAug 3, 2020
  44. Sergey OrganovAug 4, 2020
  45. Junio C HamanoAug 4, 2020
  46. Jeff KingAug 4, 2020
  47. Sergey OrganovAug 4, 2020
  48. Jeff KingAug 4, 2020
  49. Junio C HamanoAug 4, 2020
  50. Sergey OrganovAug 4, 2020
  51. Jeff KingAug 4, 2020
  52. Junio C HamanoAug 4, 2020
  53. Jeff KingAug 7, 2020
  54. Sergey OrganovAug 7, 2020
  55. Junio C HamanoAug 7, 2020
  56. Sergey OrganovAug 7, 2020
  57. Junio C HamanoAug 7, 2020
  58. Sergey OrganovAug 7, 2020
  59. Jeff KingAug 7, 2020
  60. Sergey OrganovAug 7, 2020
  61. Junio C HamanoAug 7, 2020
  62. Sergey OrganovAug 7, 2020
  63. Junio C HamanoAug 7, 2020
  64. Sergey OrganovAug 7, 2020
  65. Junio C HamanoAug 7, 2020
  66. Sergey OrganovAug 7, 2020
  67. Sergey OrganovAug 4, 2020
  68. Sergey OrganovAug 4, 2020
  69. Jeff KingAug 4, 2020
  70. Jeff KingAug 4, 2020
  71. Sergey OrganovAug 4, 2020
  72. Jeff KingAug 4, 2020
  73. Sergey OrganovAug 4, 2020
  74. Jeff KingAug 4, 2020
  75. Sergey OrganovAug 4, 2020
  76. Junio C HamanoAug 4, 2020
  77. Sergey OrganovAug 4, 2020
  78. Sergey OrganovAug 4, 2020
  79. Jeff KingAug 4, 2020
  80. revision: fix die() message for "--unpacked="Sergey Organov, Aug 4, 2020
  81. Junio C HamanoAug 5, 2020
  82. Sergey OrganovAug 5, 2020
  83. Junio C HamanoAug 5, 2020
  84. Sergey OrganovAug 5, 2020
  85. Junio C HamanoAug 5, 2020
  86. Sergey OrganovAug 5, 2020

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.