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

Re: [PATCH] Documentation/git-config.txt: reword missleading sentence

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 10, 2017, 08:48 UTC
Message-ID
<xmqqtvz7pewn.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAGb4CBUaQJOskTiXm0w+3V7E8kkaA5EiG1w0s39WDCVH-5AVoA@mail.gmail.com>
Nathan PAYRE <second.payre@gmail.com> writes:
Show 7 quoted lines
> Thanks you for the this complete answer,
> we take note of your comments.
>
> We would like to reword something else in the same line
> and we don't know what is the best way to do that properly.
> Should we do a [PATCH v2] or revert the last commit and
> commit a new one?

I'd imagine that it is in the same spirit of the old one (i.e. "let's make it less confusing"), so let's have a single patch that has both changes which is [PATCH v2].

Thanks.
Previous: Nathan PAYRENext: second.payre@gmail.com
Message 4 of 11 in “Documentation/git-config.txt: reword missleading sentence”
  1. Documentation/git-config.txt: reword missleading sentencePAYRE NATHAN p1508475, Oct 5, 2017
  2. Junio C HamanoOct 5, 2017
  3. Nathan PAYREOct 10, 2017
  4. Junio C HamanoOct 10, 2017
  5. Documentation/git-config.txt: reword missleading sentencesecond.payre@gmail.com, Oct 12, 2017
  6. Junio C HamanoOct 13, 2017
  7. Moy MatthieuOct 13, 2017
  8. Junio C HamanoOct 13, 2017
  9. Documentation/git-config.txt: reword missleading sentencePAYRE NATHAN p1508475, Oct 18, 2017
  10. Jonathan NiederOct 18, 2017
  11. Junio C HamanoOct 19, 2017

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.