From: Brad Roberts <braddr@puremagic.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [patch] fork optional branch point normazilation
Date: Sun, 17 Apr 2005 16:27:31 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0504171614150.2625-100000@bellevue.puremagic.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504171005220.7211@ppc970.osdl.org>
On Sun, 17 Apr 2005, Linus Torvalds wrote:
> On Sun, 17 Apr 2005, Brad Roberts wrote:
> >
> > (ok, author looks better, but committer doesn't obey the AUTHOR_ vars yet)
>
> They should't, but maybe I should add COMMITTER_xxx overrides. I just do
> _not_ want people to think that they should claim to be somebody else:
> it's not a security issue (you could compile your own "commit-tree.c"
> after all), it's more of a "social rule" thing. I prefer seeing bad email
> addresses that at least match the system setup to seeing good email
> addresses that people made up just to make them look clean.
>
> Mind showing what your /etc/passwd file looks like (just your own entry,
> and please just remove your password entry if you don't use shadow
> passwords).
>
> Maybe I should just remove _all_ strange characters when I do the name
> cleanup in "commit". Right now I just remove the ones that matter to
> parsing it unambiguosly: '\n' '<' and '>'.
>
> (The ',' character really is special: some people have
>
> Torvalds, Linus
>
> and maybe I should not just remove the commas, I should convert it to
> always be "Linus Torvalds". But your gecos entry is just _strange_. Why
> the extra commas, I wonder?)
>
> Linus
> -
I fully agree with the intent of the field separation, they're two very
different activities.
braddr:x:1000:1000:Brad Roberts,,,:/home/braddr:/bin/bash
All gecos entries on all my debian boxes are of the form:
fullname, office number, office extension, and home number
This is taken from the chfn man page on debian. Looking on my nearest
redhat box, the chfn man page is roughly the same. Debian's man page also
has one snippit that's not in redhat's, suggested delimiter is a ','. A
bit of searching for other platforms, aix suggests a ';' as a delimiter.
HPUX seems to want a ','.
Later,
Brad
next prev parent reply other threads:[~2005-04-17 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 12:04 [patch] fork optional branch point normazilation Brad Roberts
2005-04-17 12:25 ` Petr Baudis
2005-04-17 12:40 ` Brad Roberts
2005-04-17 17:13 ` [patch] " Linus Torvalds
2005-04-17 17:21 ` Daniel Barkalow
2005-04-17 23:27 ` Brad Roberts [this message]
2005-04-17 23:39 ` Linus Torvalds
2005-04-18 0:23 ` Petr Baudis
2005-04-18 1:07 ` Linus Torvalds
2005-04-18 1:51 ` [PATCH] remove_special() tentative fix Junio C Hamano
2005-04-18 2:01 ` [patch] fork optional branch point normazilation Brad Roberts
2005-04-18 10:45 ` Martin Schlemmer
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=Pine.LNX.4.44.0504171614150.2625-100000@bellevue.puremagic.com \
--to=braddr@puremagic.com \
--cc=git@vger.kernel.org \
--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).