From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: torvalds@osdl.org, git@vger.kernel.org
Subject: Re: What shall we do with the GECOS field again?
Date: Mon, 19 Sep 2005 09:06:21 -0700 [thread overview]
Message-ID: <7vll1trqiq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050919134838.GC2903@pasky.or.cz> (Petr Baudis's message of "Mon, 19 Sep 2005 15:48:38 +0200")
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.
What do popular MUAs do to come up with the real-name fields?
Don't they face the same problem, trying to using GECOS?
next prev parent reply other threads:[~2005-09-19 16:06 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 [this message]
2005-09-19 16:16 ` Petr Baudis
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=7vll1trqiq.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--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).