list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: Eric Sunshine <>
Cc: Derrick Stolee <>, Git List <>,
	"brian m. carlson" <>
Subject: Re: [PATCH] messages: avoid SHA-1 in end-user facing messages
Date: Fri, 14 Aug 2020 01:22:45 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Eric Sunshine's message of "Fri, 14 Aug 2020 00:51:08 -0400")

Eric Sunshine <> writes:

> On Fri, Aug 14, 2020 at 12:45 AM Junio C Hamano <> 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.


  reply	other threads:[~2020-08-14  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14  1:07 Junio C Hamano
2020-08-14  1:11 ` brian m. carlson
2020-08-14  2:21 ` Derrick Stolee
2020-08-14  4:45   ` Junio C Hamano
2020-08-14  4:51     ` Eric Sunshine
2020-08-14  8:22       ` Junio C Hamano [this message]
2020-08-14 12:21         ` Derrick Stolee
2020-08-14 16:31           ` Junio C Hamano
2020-08-14 16:40             ` [PATCH v2] " Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: [PATCH] messages: avoid SHA-1 in end-user facing messages' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).