From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Michael Haggerty <mhagger@alum.mit.edu>
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: Mon, 04 Mar 2013 09:56:26 +0100 [thread overview]
Message-ID: <vpqhakrtuf9.fsf@grenoble-inp.fr> (raw)
In-Reply-To: <vpqfw0rb25c.fsf@grenoble-inp.fr> (Matthieu Moy's message of "Wed, 20 Feb 2013 13:28:15 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> A few more random thoughts (not on my personal todo-list):
One more:
When sending commit emails, it may help to ensure that the dates are
strictly monotonic, so that the thread is seen in the right order.
IIRC, "git send-email" does this by tweaking the Date: field to make
sure there is at least one second between two emails (although they may
be actually sent at the same second). It would be cool to have the same
for git multimail.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2013-03-04 8:57 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
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 [this message]
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=vpqhakrtuf9.fsf@grenoble-inp.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=andyparkins@gmail.com \
--cc=avarab@gmail.com \
--cc=chiestand@salk.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mbranchaud@xiplink.com \
--cc=mhagger@alum.mit.edu \
--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.