From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Gerrit Pape <pape@smarden.org>,
git@vger.kernel.org, Andy Parkins <andyparkins@gmail.com>
Subject: Re: [PATCH] contrib/hooks/post-receive-email: add a From: line to the email header
Date: Thu, 08 Nov 2007 11:35:03 +0100 [thread overview]
Message-ID: <4732E657.7020202@op5.se> (raw)
In-Reply-To: <7vode52hag.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Gerrit Pape <pape@smarden.org> writes:
>
>> $committer is already extracted from the latest existing rev, so add the
>> corresponding From: line to the email header.
>
> You may fight this out with Andy if you want to, but I think I'd
> side with the existing behaviour.
>
I'm with Andy here, for the reasons stated below.
> commit e6dc8d60fbd2c84900a26545c5d360b0e202d95b
> Author: Andy Parkins <andyparkins@gmail.com>
> Date: Fri Sep 28 15:24:26 2007 +0100
>
> post-receive-hook: Remove the From field from the generated email header so that the pusher's name is used
>
> Using the name of the committer of the revision at the tip of the
> updated ref is not sensible. That information is available in the email
> itself should it be wanted, and by supplying a "From", we were
> effectively hiding the person who performed the push - which is useful
> information in itself.
>
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-11-08 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 9:48 [PATCH] contrib/hooks/post-receive-email: add a From: line to the email header Gerrit Pape
2007-11-08 9:55 ` Junio C Hamano
2007-11-08 10:35 ` Andreas Ericsson [this message]
2007-11-08 12:11 ` [PATCH] contrib/hooks/post-receive-email: remove cruft, $committer is not used Gerrit Pape
2008-01-22 14:12 ` [PATCH] contrib/hooks/post-receive-email: add a From: line to the email header Benoit Sigoure
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=4732E657.7020202@op5.se \
--to=ae@op5.se \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pape@smarden.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).