From: Derrick Stolee <firstname.lastname@example.org> To: Junio C Hamano <email@example.com>, Eric Sunshine <firstname.lastname@example.org> Cc: Git List <email@example.com>, "brian m. carlson" <firstname.lastname@example.org> Subject: Re: [PATCH] messages: avoid SHA-1 in end-user facing messages Date: Fri, 14 Aug 2020 08:21:38 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 8/14/2020 4:22 AM, Junio C Hamano wrote: > Eric Sunshine <email@example.com> writes: > >> On Fri, Aug 14, 2020 at 12:45 AM Junio C Hamano <firstname.lastname@example.org> 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". Ah, the "whitespace, not all-zeroes" is something that I misunderstood. That makes a verb change valuable in this instance. >>> 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. 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. Thanks, -Stolee
next prev parent reply other threads:[~2020-08-14 12:21 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 2020-08-14 12:21 ` Derrick Stolee [this message] 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] messages: avoid SHA-1 in end-user facing messages' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * 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: https://80x24.org/mirrors/git.git 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).