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, 08:22 UTC
Message-ID
<xmqqd03tzley.fsf@gitster.c.googlers.com>
In-Reply-To
<CAPig+cTTr8VdzeaPewktdncvnTWHjieEnEPV+vbD=GVbK7zQNQ@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 15 quoted lines
> On Fri, Aug 14, 2020 at 12:45 AM Junio C Hamano <gitster@pobox.com> wrote:
>> >> N_("Show blank SHA-1 for boundary commits (Default: off)")),
>> >> N_("Blank object names of boundary commits (Default: off)")),
>>
>> You guessed my intention correctly.  By using the word "blank" as a
>> verb (i.e. to fill the space, which should ordinarily contain
>> something meaningful, with whitespace instead), I can shorten "Show
>> blank" to compensate the lengthening of the message caused by
>> replacing "SHA-1" with "object name".
>>
>> A better phrasing to replace it is of course welcome.
>
> Perhaps?
>
>     "suppress object names of boundary commits (default: off)"

I think we want a verb that not just means to "remove" but also to "replace with the same amount of whitespace so that the overall alignment is kept". To "blank out" would mean exactly that; I do not know about "to suppress", though.

Thanks.
Previous: Eric SunshineNext: Derrick Stolee
Message 6 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.