git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Chris Hiestand <chiestand@salk.edu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add Auto-Submitted header to post-receive-email
Date: Fri, 21 Sep 2012 10:06:56 -0700	[thread overview]
Message-ID: <7v392b8fv3.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <67C048AA-0DA7-4397-A257-E0BE66089A5D@salk.edu> (Chris Hiestand's message of "Fri, 21 Sep 2012 02:04:58 -0700")

Chris Hiestand <chiestand@salk.edu> writes:

> My email in April went unanswered so I'm resending it. An Auto-Submitted header
> would be an improvement to the standard [git] post receive email.
>
> Thanks,
> Chris
>
>
> Begin forwarded message:
>
>> From: Chris Hiestand <chiestand@salk.edu>
>> Subject: [PATCH] Add Auto-Submitted header to post-receive-email
>> Date: April 14, 2012 6:15:10 PM PDT
>> To: git@vger.kernel.org, gitster@pobox.com
>> 
>> Hi,
>> 
>> I think the Auto-Submitted header is a useful hook mail header to include by default.
>> 
>> This conforms to RFC3834 and is useful in preventing e.g. vacation auto-responders
>> from replying by default.
>> 
>> Perhaps you have already considered this and decided not to include it, but I found
>> no record of such a conversation on this list.

I think the lack of response is generally lack of interest, and the
primary reason for that was because the To/Cc list did not contain
anybody who touched this particular file in the past (and no, I am
not among them; as contrib/README says, I am often the wrong person
to ask if a patch to contrib/ material makes sense).

>> From 358fc3ae1ebfd7723d54e4033d3e9a9a0322c873 Mon Sep 17 00:00:00 2001
>> From: Chris Hiestand <chiestand@salk.edu>
>> Date: Sat, 14 Apr 2012 17:58:39 -0700
>> Subject: [PATCH] Add Auto-Submitted header to post-receive-email

These four lines should not be in the body of the e-mail message
(see Documentation/SubmittingPatches).

>> Adds Auto-Submitted: auto-generated to post-receive-email header
>> This conforms to RFC3834 and is useful in preventing eg
>> vacation auto-responders from replying by default
>> ---
>> contrib/hooks/post-receive-email |    1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)

Even for contrib/ material, please always sign-off your patch (see
Documentation/SubmittingPatches).

>> 
>> diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
>> index 01af9df..282507c 100755
>> --- a/contrib/hooks/post-receive-email
>> +++ b/contrib/hooks/post-receive-email
>> @@ -237,6 +237,7 @@ generate_email_header()
>> 	X-Git-Reftype: $refname_type
>> 	X-Git-Oldrev: $oldrev
>> 	X-Git-Newrev: $newrev
>> +	Auto-Submitted: auto-generated
>> 
>> 	This is an automated email from the git hooks/post-receive script. It was
>> 	generated because a ref change was pushed to the repository containing

I think the choice of "auto-generated" is a sensible one, as
responding to a 'push' is like triggered by 'cron'.

I'd however appreciate comments from people who either worked on
this code or list regulars who actually use this code in the
production.

Thanks.

  reply	other threads:[~2012-09-21 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15  1:15 [PATCH] Add Auto-Submitted header to post-receive-email Chris Hiestand
2012-09-21  9:04 ` Chris Hiestand
2012-09-21 17:06   ` Junio C Hamano [this message]
2013-01-16 17:29     ` Chris Hiestand
2013-01-17  0:49       ` Jonathan Nieder

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=7v392b8fv3.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=chiestand@salk.edu \
    --cc=git@vger.kernel.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).