All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org, Andy Parkins <andyparkins@gmail.com>,
	Sitaram Chamarty <sitaramc@gmail.com>
Subject: Re: [RFC] Add a new email notification script to "contrib"
Date: Mon, 16 Jul 2012 18:48:12 +0200	[thread overview]
Message-ID: <500445CC.2020404@alum.mit.edu> (raw)
In-Reply-To: <vpqhat7wujb.fsf@bauges.imag.fr>

On 07/16/2012 06:16 PM, Matthieu Moy wrote:
> mhagger@alum.mit.edu writes:
>
>> From: Michael Haggerty <mhagger@alum.mit.edu>
>>
>> Add a new Python script, contrib/hooks/post-receive-multimail.py, that
>> can be used to send notification emails describing pushes into a git
>> repository.  This script is derived from
>> contrib/hooks/post-receive-mail, but has many differences, including:
>>
>> * One email per commit [1].
>
> It's cool to have it, but it would be nice to allow the "one email per
> push" mode too. I have co-workers who already complain about the number
> of emails sent by the post-receive-mail script. I can't imagine their
> reaction if I set up a one-email-per-commit hook ;-).

It's already supported:

     git config hooks.announcelist \
         "nosy@example.com, overwhelmed@example.com, phb@example.com"
     git config hooks.refchangelist \
         "nosy@example.com, overwhelmed@example.com"
     git config hooks.commitlist "nosy@example.com"

Granted, the ReferenceChange emails currently cannot be configured to 
include diffs, as can those of the old post-receive-email script, and 
the text alludes to upcoming one-email-per-commit emails.  But since it 
looks like the new script might be put forward as a replacement for the 
old one, I will obviously put more work into supporting as much of the 
old functionality as possible.

Thanks for the feedback!

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2012-07-16 16:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14  6:59 [RFC] Add a new email notification script to "contrib" mhagger
2012-07-14  9:46 ` Stefan Näwe
     [not found]   ` <CALUzUxoi-X2nTTFF7utJz2DOTDE8-s7QOgR=HmQAkOVkGY17BA@mail.gmail.com>
2012-07-14 12:03     ` Stefan Naewe
2012-07-15  4:38   ` Michael Haggerty
2012-07-15  7:11 ` Junio C Hamano
2012-07-15 22:45   ` Michael Haggerty
2012-07-16 15:57 ` Marc Branchaud
2012-07-16 16:38   ` Michael Haggerty
2012-07-16 16:16 ` Matthieu Moy
2012-07-16 16:48   ` Michael Haggerty [this message]
2012-07-16 17:47     ` Junio C Hamano
2012-07-16 19:05       ` Michael Haggerty
2012-07-16 19:21         ` Junio C Hamano
2012-07-18  7:52 ` Matthieu Moy
2012-07-20 10:01 ` Michael Haggerty
2012-11-07 21:47   ` Ævar Arnfjörð Bjarmason
2012-11-08  9:42     ` Michael Haggerty
2012-11-08 11:39       ` Ævar Arnfjörð Bjarmason
2012-11-08 12:17         ` Michael Haggerty
2012-11-08 15:38           ` Ævar Arnfjörð Bjarmason
2012-11-22  7:32             ` Michael Haggerty
2012-11-08 16:24           ` Marc Branchaud
2012-11-08 16:37             ` Ævar Arnfjörð Bjarmason
2012-11-08 16:46               ` Marc Branchaud
2012-11-08 16:03       ` Marc Branchaud
2012-11-22  7:27         ` Michael Haggerty

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=500445CC.2020404@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sitaramc@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.