git/list[1] front-page[2] threads[3] people[4] search[5] about
 

What shall we do with the GECOS field again?

From
Petr Baudis <pasky@suse.cz>
Date
Sep 19, 2005, 13:48 UTC
Message-ID
<20050919134838.GC2903@pasky.or.cz>
  Hello,
  after today's another confrontation with angry mob of real-world
Cogito users, I decided to revive the old discussion about what part of
the GECOS field should be used to prefill GIT_*_NAME. Linus stated in
<Pine.LNX.4.58.0504171636590.7211@ppc970.osdl.org> that he does not want
to cut based on ',', because it might throw away the first name of gecos
fields in the "Torvalds, Linus" name.
  Well, I have to say that from the GECOS fields I saw, none use that
format, but a lot of them used the realname,phone,something,phone,...
format. The other point is, that users usually do not expect their phone
number to end up in their name information in GIT commits, which results
in a very unpleasant surprise (doubly so due to the immutable GIT
nature). Yes, they should check after the first commit if they are happy
with everything, and yes, GECOS is world-readable and therefore they
shouldn't put information they don't want to be public to it. Still they
do and I think GIT shouldn't make them unpleasant surprises.
  So my proposal (patch will follow soon) is to cut everything after the
first , or ; from the GECOS field. These are the usual delimiters used
in the GECOS field, and hopefully this will prevent polluting the
realname fields of commit headers with crap and surprising the users.
In the (I think rather rare) situation of the "Baudis, Petr"-like GECOS
fields, this will just result in only the surname being in the realname
field, which seems to be much less harmful and comparably less evil to
me. 
  Opinions?
-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox
Next: Kevin O'Riordan
Message 1 of 20 in “What shall we do with the GECOS field again?”
  1. Petr BaudisSep 19, 2005
  2. Kevin O'RiordanSep 19, 2005
  3. Matthias UrlichsSep 19, 2005
  4. A Large Angry SCMSep 19, 2005
  5. Matthias UrlichsSep 19, 2005
  6. A Large Angry SCMSep 19, 2005
  7. Petr BaudisSep 19, 2005
  8. Junio C HamanoSep 19, 2005
  9. Petr BaudisSep 19, 2005
  10. Linus TorvaldsSep 19, 2005
  11. Junio C HamanoSep 19, 2005
  12. Linus TorvaldsSep 19, 2005
  13. Ryan AndersonSep 20, 2005
  14. Linus TorvaldsSep 20, 2005
  15. Junio C HamanoSep 20, 2005
  16. Nikolai WeibullSep 19, 2005
  17. Nikolai WeibullSep 19, 2005
  18. Junio C HamanoSep 20, 2005
  19. Junio C HamanoSep 20, 2005
  20. Nikolai WeibullSep 20, 2005

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.