From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matt Kraai <kraai@ftbfs.org>,
git@vger.kernel.org, Matt Kraai <kraai@asturias.ftbfs.org>
Subject: Re: [PATCH] Use /etc/mailname for the hostname part of the email address.
Date: Fri, 06 Jul 2007 23:07:42 -0700 [thread overview]
Message-ID: <7vabu8d9w1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <alpine.LFD.0.999.0707061945220.31544@woody.linux-foundation.org> (Linus Torvalds's message of "Fri, 6 Jul 2007 19:54:34 -0700 (PDT)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> The thing is, I actually personally tend to _prefer_ the committer name as
> being "user@hostname" rather than a "real" email address.
>
> It often tells you something much more.
I remember you said exactly the same thing before. But I wonder
if "committer" e-mail address is really the place you would want
to use as (one of) the source of reliable information for that
kind of thing. The information obviously can be used among
people who exchange commits via git-pull, but what about people
whose changes are always fed as e-mailed patches?
For such people, if they would want to encode the auxiliary
information in their author name like you do with g5 and woody,
would you recommend they put the in-body From: header, which may
not be working e-mail addresses to reach them?
prev parent reply other threads:[~2007-07-07 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 2:21 [PATCH] Use /etc/mailname for the hostname part of the email address Matt Kraai
2007-07-07 2:54 ` Linus Torvalds
2007-07-07 6:07 ` Junio C Hamano [this message]
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=7vabu8d9w1.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kraai@asturias.ftbfs.org \
--cc=kraai@ftbfs.org \
--cc=torvalds@linux-foundation.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