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

Re: [PATCH v3] rebase --merge: optionally skip upstreamed commits

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 30, 2020, 16:49 UTC
Message-ID
<xmqq1rp9aiuv.fsf@gitster.c.googlers.com>
In-Reply-To
<e917f451-c00a-c819-7f78-888ba6e8f5ea@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
Show 11 quoted lines
>> +--keep-cherry-pick::
>> +--no-keep-cherry-pick::
>
> I noticed that this _could_ have been simplified to
>
> 	--[no-]keep-cherry-pick::
>
> but I also see several uses of either in our documentation. Do we
> have a preference? By inspecting the lines before a "no-" string,
> I see that some have these two lines, some use the [no-] pattern,
> and others highlight the --no-<option> flag completely separately.

"git log -S'--[no-]' Documentation/" (and its "-S'--no-'" variant) tell us that many of our recent commits do prefer the single-line form, but then in d333f672 (git-checkout.txt: spell out --no-option, 2019-03-29), we see we turned a handful of "--[no-]option" into "--option" followed by "--no-option" deliberately [*1*].

So, we do not seem to have a strong concensus.

I think all the new ones that spell --no-option:: out are the ones when --option:: and --no-option:: have their own paragraph, e.g. "--sign/--no-sign" of "git-tag".

As the differences do not matter all that much, I do not mind declaring (and one of the tasks of the maintainer is to make a declaration on such a choice that it matters more for us to pick either one and we all sticking to it, rather than which choice we make) that we'd prefer the expanded two-liner form (which when formatted would become a single line with two things on it) and mark the task to convert from '--[no-]option' as #leftoverbit.

Thanks for your attention to the details.
[Footnote]

*1* The justification given was that it makes is it is easier to search that way and it is less cryptic. Personally I do not think it matters that much. Even when trying to learn what the negated form does, nobody would look for "--no-keep-ch" to find the above paragraph. "keep-cherry-pick" would be what they would look for, with or without leading double-dashes.

Previous: Derrick StoleeNext: Jonathan Tan
Message 27 of 36 in “rebase --merge: optionally skip upstreamed commits”
  1. rebase --merge: optionally skip upstreamed commitsJonathan Tan, Mar 9, 2020
  2. Taylor BlauMar 10, 2020
  3. Jonathan TanMar 10, 2020
  4. Johannes SchindelinMar 10, 2020
  5. Jonathan TanMar 10, 2020
  6. Elijah NewrenMar 10, 2020
  7. Jonathan TanMar 10, 2020
  8. Jonathan TanMar 12, 2020
  9. Elijah NewrenMar 12, 2020
  10. Elijah NewrenMar 14, 2020
  11. Jonathan TanMar 17, 2020
  12. rebase --merge: optionally skip upstreamed commitsJonathan Tan, Mar 18, 2020
  13. Junio C HamanoMar 18, 2020
  14. Jonathan TanMar 18, 2020
  15. Junio C HamanoMar 18, 2020
  16. Elijah NewrenMar 18, 2020
  17. Junio C HamanoMar 18, 2020
  18. Elijah NewrenMar 19, 2020
  19. Junio C HamanoMar 18, 2020
  20. Jonathan TanMar 26, 2020
  21. Elijah NewrenMar 26, 2020
  22. Junio C HamanoMar 26, 2020
  23. rebase --merge: optionally skip upstreamed commitsJonathan Tan, Mar 30, 2020
  24. Junio C HamanoMar 30, 2020
  25. Danh DoanMar 30, 2020
  26. Derrick StoleeMar 30, 2020
  27. Junio C HamanoMar 30, 2020
  28. Jonathan TanMar 30, 2020
  29. Derrick StoleeMar 31, 2020
  30. Elijah NewrenMar 31, 2020
  31. Junio C HamanoMar 31, 2020
  32. Junio C HamanoMar 31, 2020
  33. Jonathan TanApr 10, 2020
  34. Elijah NewrenApr 11, 2020
  35. Jonathan TanApr 11, 2020
  36. Elijah NewrenApr 11, 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.