From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [Cogito] Various bugs
Date: Tue, 7 Feb 2006 07:53:57 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602070751410.3854@g5.osdl.org> (raw)
In-Reply-To: <7v8xsn50rf.fsf@assigned-by-dhcp.cox.net>
On Mon, 6 Feb 2006, Junio C Hamano wrote:
>
> It depends on what you expect, but it meets _my_ expectation:
>
> $ GIT_AUTHOR_NAME='' git-commit-tree $(git-write-tree) </dev/null
> Committing initial tree a2b59c3848164a2c9c3c75fbaadccaed9485da92
> ef90563fa278735af367e7606ea7eb2559121ca7
> $ git-cat-file commit ef90563fa278735af367e7606ea7eb2559121ca7
> tree a2b59c3848164a2c9c3c75fbaadccaed9485da92
> author <junkio@cox.net> 1139281078 -0800
> committer Junio C Hamano <junkio@cox.net> 1139281078 -0800
>
> That is, the user said GIT_AUTHOR_NAME is empty, so he gets a
> commit with an empty author name.
Yes. That said, we should probably disallow that in git-commit-tree (and
let the user fix it up some way).
> get_ident() in ident.c does this. getenv("GIT_AUTHOR_NAME") and
> friends are passed to it, and git_default_* are takenfrom gecos.
> It might match some peoples' expectation (but not mine) if we
> did this instead.
No, don't use the default name.
An empty GIT_AUTHOR_NAME should _not_ mean that we use the default name
(which is usually the committer), because rather than meaning "default",
it most likely means "buggy import script".
I'd rather have an email import of mine say that it cannot commit, than
have it put "Linus Torvalds" in the author line (and some random email).
Linus
next prev parent reply other threads:[~2006-02-07 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 4:13 [Cogito] Various bugs Jonas Fonseca
2006-02-07 0:36 ` Petr Baudis
2006-02-07 2:03 ` Junio C Hamano
2006-02-07 2:10 ` Petr Baudis
2006-02-07 3:03 ` Junio C Hamano
2006-02-07 15:53 ` Linus Torvalds [this message]
2006-02-07 16:49 ` Petr Baudis
2006-02-07 16:56 ` Linus Torvalds
2006-02-07 20:49 ` Junio C Hamano
2006-02-07 13:55 ` Jonas Fonseca
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.64.0602070751410.3854@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).