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

Re: [PATCH] doc: sparse-checkout: Fix list markers

From
Junio C Hamano <gitster@pobox.com>
Date
May 30, 2025, 13:38 UTC
Message-ID
<871ps6b4n8.fsf@gitster.g>
In-Reply-To
<CAPig+cQbchWLMH+pTVfLHwFshaex2vhC8Pk57EC4U-vch00ZDA@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 7 quoted lines
> You're welcome to submit an additional patch implementing Kristoffer's
> suggestion. Normally, it would make sense to send them both as a
> two-patch series, however, I'm not so sure that that would be a good
> idea in this case. The reason I question it is that the original patch
> is an obvious and uncontroversial fix, however, Kristoffer's
> suggestion -- because it is a subjective change -- may get pushback
> from reviewers.

I had the same thought. If I were working on this topic, I'd send the original as-is with the suggested name fix, let it graduate, and then after all the dust settled, do enumeration-style changes as a new and totally independent patch, which may cover enumerations other than this single instance.

Thanks.
Previous: oneeeNext: Patrick Steinhardt
Message 8 of 11 in “doc: sparse-checkout: Fix list markers”
  1. doc: sparse-checkout: Fix list markersoneee via GitGitGadget, Apr 21, 2025
  2. Kristoffer HaugsbakkMay 28, 2025
  3. Eric SunshineMay 28, 2025
  4. Kristoffer HaugsbakkMay 28, 2025
  5. oneeeMay 30, 2025
  6. Eric SunshineMay 30, 2025
  7. oneeeMay 30, 2025
  8. Junio C HamanoMay 30, 2025
  9. Patrick SteinhardtMay 28, 2025
  10. doc: sparse-checkout: use consistent inline list styleoneee via GitGitGadget, May 30, 2025
  11. Kristoffer HaugsbakkMay 30, 2025

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.