git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: torvalds@osdl.org, git@vger.kernel.org
Subject: Re: What shall we do with the GECOS field again?
Date: Mon, 19 Sep 2005 18:16:36 +0200	[thread overview]
Message-ID: <20050919161636.GA18320@pasky.or.cz> (raw)
In-Reply-To: <7vll1trqiq.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Mon, Sep 19, 2005 at 06:06:21PM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> Petr Baudis <pasky@suse.cz> writes:
> 
> >   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.
> 
> >   Opinions?
> 
> If the real world GECOS were either only plain and
> name,room,blah,... format as you say and assume I think a
> heuristics like you suggested would be better than the
> current heuristics of assuming everything is a name, but I
> haven't seen what "angry mob" actually has so cannot judge.

It uses the name,room,blah,... format.

> What do popular MUAs do to come up with the real-name fields?
> Don't they face the same problem, trying to using GECOS?

mutt:

  { "gecos_mask",       DT_RX,   R_NONE, UL &GecosMask, UL "^[^,]*" },

A regular expression used by mutt to parse the GECOS field of a password
entry when expanding the alias.  By default the regular expression is
set to "^[^,]*" which will return the string up to the first ","
encountered.  If the GECOS field contains a string like "lastname,
firstname" then you should set the gecos_mask=".*".

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox

  reply	other threads:[~2005-09-19 16:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 13:48 What shall we do with the GECOS field again? Petr Baudis
2005-09-19 14:11 ` Kevin O'Riordan
2005-09-19 14:34   ` Matthias Urlichs
2005-09-19 14:30 ` A Large Angry SCM
2005-09-19 14:47   ` Matthias Urlichs
2005-09-19 16:16     ` A Large Angry SCM
2005-09-19 16:34       ` Petr Baudis
2005-09-19 16:06 ` Junio C Hamano
2005-09-19 16:16   ` Petr Baudis [this message]
2005-09-19 16:32   ` Linus Torvalds
2005-09-19 16:49     ` Junio C Hamano
2005-09-19 16:59       ` Linus Torvalds
2005-09-20  4:02         ` Ryan Anderson
2005-09-20  4:13           ` Linus Torvalds
2005-09-20  3:12       ` Horst von Brand
2005-09-20  6:30       ` Junio C Hamano
2005-09-19 16:32 ` Nikolai Weibull
2005-09-19 21:21   ` Nikolai Weibull
2005-09-20  7:10     ` Junio C Hamano
2005-09-20  1:53   ` Junio C Hamano
2005-09-20 10:31     ` Nikolai Weibull

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

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

  git send-email \
    --in-reply-to=20050919161636.GA18320@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).