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
brian m. carlson <sandals@crustytoothpaste.net>
Date
Aug 14, 2020, 01:11 UTC
Message-ID
<20200814011133.GJ8085@camp.crustytoothpaste.net>
In-Reply-To
<xmqqy2miyr0f.fsf@gitster.c.googlers.com>
On 2020-08-14 at 01:07:12, Junio C Hamano wrote:
Show 6 quoted lines
> There are still a handful mentions of SHA-1 when we meant the
> (hexadecimal) object names in end-user facing messages.  Rewrite
> them.
> 
> I was hoping that this can mostly be s/SHA-1/object name/, but
> a few messages needed rephrasing to keep the result readable.

All of these seem reasonable, and I think "object name" is fine for this purpose.

-- 
brian m. carlson: Houston, Texas, US
Previous: Junio C HamanoNext: Derrick Stolee
Message 2 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.