From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
git@vger.kernel.org, "Chris Hiestand" <chrishiestand@gmail.com>,
"Marc Branchaud" <mbranchaud@xiplink.com>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
"Michiel Holtkamp" <git@elfstone.nl>,
"Stefan Näwe" <stefan.naewe@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH v3 0/1] git-multimail: a replacement for post-receive-email
Date: Sun, 21 Apr 2013 15:12:04 -0700 [thread overview]
Message-ID: <7va9orsfd7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <517445E5.3080304@alum.mit.edu> (Michael Haggerty's message of "Sun, 21 Apr 2013 22:02:45 +0200")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> That seems very workable.
That is pretty much it.
> What is your preference regarding the history to date?
The only thing I deeply care about is that initial and subsequent
"git pull" I'll do from you [*1*] will pull in commits that touch
only the "multimail" part in the contrib/ area and not mixed with
unrelated changes to other areas.
If the history you have so far would later help others learn the
motivation, design, constraints etc. while developing it, which
cannot be easily read from the resulting code, i.e. help maintaining
it in general, it's a good idea to keep it. In such a case,
however, people may want to review that history as well.
If it is the "oops, it didn't work, let's try another" kind of
"record as we build" type of history that may not help the future
maintainace that much, you may instead want to start with a single
code-dump "here is the first public version" (which is reviewed in
this thread, I think) without the history behind it.
Your choice, in other words ;-)
[Footnote]
*1* This does not even have to be a stable URL I would place in
remote.multimail.url configuration; it does not even have to be a
non-rewinding tree.
next prev parent reply other threads:[~2013-04-21 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 10:49 [PATCH v3 0/1] git-multimail: a replacement for post-receive-email Michael Haggerty
2013-04-21 10:56 ` Jonathan Nieder
2013-04-21 18:44 ` Junio C Hamano
2013-04-21 20:02 ` Michael Haggerty
2013-04-21 22:12 ` Junio C Hamano [this message]
2013-04-21 22:28 ` Junio C Hamano
[not found] ` <1366541380-10786-2-git-send-email-mhagger@alum.mit.edu>
2013-04-21 11:07 ` [PATCH v3 1/1] " Jonathan Nieder
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=7va9orsfd7.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=chrishiestand@gmail.com \
--cc=git@elfstone.nl \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mbranchaud@xiplink.com \
--cc=mhagger@alum.mit.edu \
--cc=stefan.naewe@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).