From: "Stephen Sinclair" <radarsat1@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add committer and author names to top of COMMIT_EDITMSG.
Date: Fri, 11 Jan 2008 20:33:23 -0500 [thread overview]
Message-ID: <9b3e2dc20801111733o477b3aadv6ee76d3aafade54a@mail.gmail.com> (raw)
In-Reply-To: <7vbq7r28qo.fsf@gitster.siamese.dyndns.org>
> * If AUTHOR_NAME+EMAIL is different from AUTHOR_NAME+EMAIL that
> I would normally get for myself, or
I thought of this, however if the purpose of this is to handle a case
where you do a commit from a new and unconfigured user account, "that
I would normally get for myself" is undefined, since this information
is (rightfully) not propagated by git-clone. This is why I made it
unconditional, (or perhaps something you could could turn off, but
would by default be on), but I figured there would be objections since
I admit it's not always useful information.
> * If AUTHOR_NAME+EMAIL contains garbage identifier commonly
> found when misconfigured (e.g. ".(none)" at the end of
> e-mail),
That's more interesting to me. I just checked my logs and I do see
that in at least one case, this .(none) was not appended. The
computer in question was configured (not by me) with a domain of
".local", so the commit has <machinename>.local as part of the email
address. However I would imagine this might solve most cases.
I still don't understand why git generates a default email address
instead of just giving an error message; do people actually use this
scenario? In my experience an email address must always be explicitly
given, but perhaps some people work on the machines that also receive
their mail. I rarely do "real" work on an actual server, but I guess
some people do. I think they must be in the minority though..
On the other hand, now that I've been thinking about it I think my
idea of simply configuring a hook in my personal central git is
probably an easier and all-round better solution to my problem. I
understand that git relies on system accounts for security, but
there's no reason I can't configure a particular repo to issue a
warning when it receives incoming commits from an unknown user/email.
Steve
next prev parent reply other threads:[~2008-01-12 1:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 20:10 [PATCH] Add committer and author names to top of COMMIT_EDITMSG Stephen Sinclair
2008-01-11 21:26 ` Johannes Schindelin
2008-01-11 23:36 ` Junio C Hamano
2008-01-12 0:09 ` Stephen Sinclair
2008-01-12 0:22 ` Junio C Hamano
2008-01-12 1:33 ` Stephen Sinclair [this message]
2008-01-12 1:53 ` Junio C Hamano
2008-01-12 2:25 ` Stephen Sinclair
2008-01-12 4:57 ` Junio C Hamano
2008-01-12 7:26 ` Stephen Sinclair
2008-01-12 8:02 ` Junio C Hamano
2008-01-12 4:52 ` Jeff King
2008-01-12 5:06 ` Junio C Hamano
2008-01-12 5:30 ` Junio C Hamano
2008-01-12 5:32 ` Jeff King
2008-01-12 5:56 ` Junio C Hamano
2008-01-12 5:58 ` Jeff King
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=9b3e2dc20801111733o477b3aadv6ee76d3aafade54a@mail.gmail.com \
--to=radarsat1@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).