Re: What shall we do with the GECOS field again?

From: Matthias Urlichs <smurf@smurf.noris.de>
Date: Sep 19, 2005, 14:47 UTC
Message-ID: <pan.2005.09.19.14.47.51.811409@smurf.noris.de>
In-Reply-To: <432ECB92.5000505@gmail.com>

Hi, A Large Angry SCM wrote:

> Saying that the user's name is first and a particular punctuation 
> character SHALL be the standard cut point and everyone not happy with 
> the results should explicitly set the Git environment variables is the 
> wrong approach.

I disagree. Standard add-user tools use the gecos field in one of two ways:
- fullname
- fullname,and,some,other,cruft

Sure, many organizations bake their own, but I'd argue that the majority doesn't.

> AND/OR to include 
> the what Git thinks the user's name name might be in the commit message
> template they're editing (like the file list).

I think that's a good idea, as long as people are told how to change it (i.e., an envvar -- NOT by editing the file).

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
On those occasions when the angel managed to get his mind into the
twentieth century, it always gravitated to 1950.
        -- (Terry Pratchett & Neil Gaiman, Good Omens)