Re: [RFC v2] git-multimail: a replacement for post-receive-email
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Feb 20, 2013, 12:28 UTC
- Message-ID
- <vpqfw0rb25c.fsf@grenoble-inp.fr>
- In-Reply-To
- <5104E738.602@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
> A while ago, I submitted an RFC for adding a new email notification > script to "contrib" [1].
We've discussed offline with Michael, a few patches have been merged, and there are still a few pending pull requests. I liked the script already, but it's getting even cooler ;-).
A few more random thoughts (not on my personal todo-list):
* It may make sense to add the short sha1 of the new reference in email titles (branch foo updated -> branch foo updated to $sha1), so that gmail users do not get a single huge thread "branch foo updated".
(Yes, I do know about the Reference field, but gmail uses Subject: for threading).
* Perhaps we should allow a per-branch configuration, like
[multimailhook]
mailingList = some@list.com
[multimailhook "refs/heads/my-branch"]
mailingList = some-other@list.com
<whateverOtherConfig> = <whateverOtherValue>Branch specific would override value for Config.get(), and Config.get_all() should probably list both the branch-specific and the other keys.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/