From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
"Trond Hasle Amundsen" <t.h.amundsen@usit.uio.no>,
git@vger.kernel.org, "Marc Branchaud" <mbranchaud@xiplink.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Chris Hiestand" <chiestand@salk.edu>
Subject: Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config
Date: Tue, 07 May 2013 09:46:45 +0200 [thread overview]
Message-ID: <5188B165.3050709@alum.mit.edu> (raw)
In-Reply-To: <7vwqrbmh4d.fsf@alter.siamese.dyndns.org>
On 05/07/2013 08:36 AM, Junio C Hamano wrote:
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>
>> More precisely: you should have a look at git-multimail (in directory
>> contrib/, in branch for now pu/, or from
>> https://github.com/mhagger/git-multimail) before spending time on
>> post-receive-email.
>
> Oh, by the way, is this a vote of confidence in that topic, hinting
> that we would want to advance it to 'next'?
>
> As it is only adding a new script to contrib/, it could be argued
> that we could even push it to 1.8.3-rc1, but until I hear from the
> original author (who will be the champion for that corner of the
> contrib/ area), I wouldn't do so.
My understanding is that we are waiting on two things:
1. Consensus from the community. I would characterize the feedback on
the mailing list as limited in quantity but strongly positive [1-4] and
I think that most/all of the wishes for post-receive-email features that
were originally omitted from git-multimail have been implemented in the
current version. Some of the mailing list feedback was about earlier
versions. Do you want people to give feedback specifically about the
current version?
2. For me to figure out what part of the git-multimail history I think
should be included in the Git project, do any necessary repository
rewriting, and submit a pull request to you. The fact that I haven't
gotten to this is due to the fact that I've been busy getting git-imerge
[5] ready to present at GitMerge.
Michael
[1] http://article.gmane.org/gmane.comp.version-control.git/209168
(Branchaud)
[2] http://article.gmane.org/gmane.comp.version-control.git/214941
(Bjarmason)
[3] http://article.gmane.org/gmane.comp.version-control.git/214987
(Hiestand)
[4] http://article.gmane.org/gmane.comp.version-control.git/216705 (Moy)
[5] https://github.com/mhagger/git-imerge
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2013-05-07 7:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 13:53 [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config Trond Hasle Amundsen
2013-05-06 15:22 ` Trond Hasle Amundsen
2013-05-06 15:36 ` Junio C Hamano
2013-05-06 15:42 ` Matthieu Moy
2013-05-06 16:29 ` Trond Hasle Amundsen
2013-05-07 6:36 ` Junio C Hamano
2013-05-07 7:46 ` Michael Haggerty [this message]
2013-05-07 15:15 ` Junio C Hamano
2013-05-07 15:36 ` Matthieu Moy
2013-07-01 21:58 ` Junio C Hamano
2013-07-02 9:12 ` Michael Haggerty
2013-07-02 18:51 ` Junio C Hamano
2013-05-07 7:49 ` Matthieu Moy
2013-05-07 14:51 ` Junio C Hamano
2013-05-06 16:26 ` Trond Hasle Amundsen
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=5188B165.3050709@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=chiestand@salk.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mbranchaud@xiplink.com \
--cc=t.h.amundsen@usit.uio.no \
/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).