mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <>
To: Junio C Hamano <>
Subject: Re: [PATCH] doc: provide guidance on format
Date: Sun, 15 Sep 2019 22:57:34 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]

On 2019-09-15 at 22:18:07, Junio C Hamano wrote:
> "brian m. carlson" <> writes:
> > diff --git a/Documentation/git-commit-tree.txt b/Documentation/git-commit-tree.txt
> > index 4b90b9c12a..34a8496b0e 100644
> > --- a/Documentation/git-commit-tree.txt
> > +++ b/Documentation/git-commit-tree.txt
> > @@ -92,6 +92,12 @@ if set:
> >  
> >  (nb "<", ">" and "\n"s are stripped)
> >  
> > +The author and committer names are by convention some form of a personal name,
> > +as opposed to a username, although Git does not enforce or require any
> > +particular form.
> I have a lot of trouble with 'username' in the context of this
> paragraph.
> After all, you are describing the name appropriate to be set as the
> value of the configuration, and you are trying to stress
> that the name used there is different from and has nothing to do
> with the name machines use to identify the user.  In the paragraph
> that follows this new paragraph, there is a reference to "system
> user name", which is still not great but probably better than
> "username" above.  Perhaps there is a term that is distinct enough
> from "user name" that is commonly used I am forgetting?  I am almost
> tempted to say "user id", but there must be even better phrases.  I
> dunno.

I wonder if we should just omit that aside, then, since I'm not sure of
a less ambiguous term for "how I identify myself to a computer".  I think
describing the convention as "some form of a personal name" is probably
sufficient to tell people what we suggest they do.

My first draft of that sentence didn't include the part within the
commas at all.
brian m. carlson: Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

      reply	other threads:[~2019-09-15 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14 21:02 [PATCH] doc: provide guidance on format brian m. carlson
2019-09-15 22:18 ` Junio C Hamano
2019-09-15 22:57   ` brian m. carlson [this message]

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 \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).