From: Michael Haggerty <mhagger@alum•mit.edu>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
Cc: "git discussion list" <git@vger•kernel.org>,
"Andy Parkins" <andyparkins@gmail•com>,
"Sitaram Chamarty" <sitaramc@gmail•com>,
"Junio C Hamano" <gitster@pobox•com>,
"Marc Branchaud" <mbranchaud@xiplink•com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
"Chris Hiestand" <chiestand@salk•edu>
Subject: Re: [RFC v2] git-multimail: a replacement for post-receive-email
Date: Sun, 24 Feb 2013 06:31:31 +0100 [thread overview]
Message-ID: <5129A5B3.7020807@alum.mit.edu> (raw)
In-Reply-To: <vpqfw0rb25c.fsf@grenoble-inp.fr>
On 02/20/2013 01:28 PM, Matthieu Moy wrote:
> Michael Haggerty <mhagger@alum•mit.edu> writes:
>> A while ago, I submitted an RFC for adding a new email notification
>> script to "contrib" [...]
>
> 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).
> [...]
I just implemented this in branch sha1s-in-subject [1]. Please let me
know if this works for you then I'll merge it to master. (It depends on
the header-handling branch, which also includes your patch for non-ASCII
header fields.)
Michael
[1] https://github.com/mhagger/git-multimail/tree/sha1s-in-subject
--
Michael Haggerty
mhagger@alum•mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2013-02-24 5:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 8:37 [RFC v2] git-multimail: a replacement for post-receive-email Michael Haggerty
2013-01-29 15:25 ` Ævar Arnfjörð Bjarmason
2013-01-30 2:27 ` Chris Hiestand
2013-02-13 14:56 ` Matthieu Moy
2013-02-13 15:26 ` Andy Parkins
2013-02-13 16:12 ` Matthieu Moy
2013-02-13 21:42 ` Michael Haggerty
2013-02-14 12:55 ` Matthieu Moy
2013-02-15 5:07 ` Michael Haggerty
2013-02-20 12:28 ` Matthieu Moy
2013-02-24 5:31 ` Michael Haggerty [this message]
2013-02-25 9:54 ` Matthieu Moy
2013-02-25 10:50 ` Michael Haggerty
2013-03-09 5:32 ` Michael Haggerty
2013-02-24 5:53 ` Michael Haggerty
2013-02-25 10:01 ` Matthieu Moy
2013-03-04 8:56 ` Matthieu Moy
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=5129A5B3.7020807@alum.mit.edu \
--to=mhagger@alum$(echo .)mit.edu \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=andyparkins@gmail$(echo .)com \
--cc=avarab@gmail$(echo .)com \
--cc=chiestand@salk$(echo .)edu \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=mbranchaud@xiplink$(echo .)com \
--cc=sitaramc@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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