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

Re: [PATCH] messages: avoid SHA-1 in end-user facing messages

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 14, 2020, 16:31 UTC
Message-ID
<xmqq8sehyysl.fsf@gitster.c.googlers.com>
In-Reply-To
<5e9805f4-81c0-39bc-463a-8c47872f6456@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
Show 6 quoted lines
> What about something as simple as:
>
> 	"Do not show object names of boundary commits (Default: off)"
>
> While this doesn't imply that the object name positions are filled with
> whitespace, that is just a formatting concern.
Nice.  I like messages that stick to simple and easy words.
Thanks.
Previous: Derrick StoleeNext: Junio C Hamano
Message 8 of 9 in “messages: avoid SHA-1 in end-user facing messages”
  1. messages: avoid SHA-1 in end-user facing messagesJunio C Hamano, Aug 14, 2020
  2. brian m. carlsonAug 14, 2020
  3. Derrick StoleeAug 14, 2020
  4. Junio C HamanoAug 14, 2020
  5. Eric SunshineAug 14, 2020
  6. Junio C HamanoAug 14, 2020
  7. Derrick StoleeAug 14, 2020
  8. Junio C HamanoAug 14, 2020
  9. messages: avoid SHA-1 in end-user facing messagesJunio C Hamano, Aug 14, 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.