From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
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 21:05:07 +0200 [thread overview]
Message-ID: <500465E3.8040501@alum.mit.edu> (raw)
In-Reply-To: <7vtxx738dz.fsf@alter.siamese.dyndns.org>
On 07/16/2012 07:47 PM, Junio C Hamano wrote:
> Michael Haggerty <mhagger@alum.mit.edu> writes:
>
>> 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"
>
> Sad. Is the "post-recieve email" squatting on the _whole_ hooks.*
> namespace, not postreceiveemailhook.* or something more reasonably
> limited?
Yes. I didn't like this either, but I copied this aspect of the old
script in the interest of compatibility.
If we want to change this, now would be a good time, before the new
script starts using more of the hooks namespace. One could choose a new
namespace and deprecate the old one, optionally in multiple steps:
1. Only read new options from new namespace; read old options from new
namespace or (if the new names are not set) falling back to the old
namespace.
2. Deprecate the old namespace, emitting warnings if the old names are
still set but continuing to use them.
3. Stop supporting the old namespace, but emit warnings if the old names
are still set.
4. Stop looking in the old namespace altogether.
Though, given that hook scripts have to be enabled/upgraded
per-repository, usually on a central server, probably doing only steps 2
and 4 would be enough.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2012-07-16 19:05 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
2012-07-16 17:47 ` Junio C Hamano
2012-07-16 19:05 ` Michael Haggerty [this message]
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=500465E3.8040501@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).