From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
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 08:15:43 -0700 [thread overview]
Message-ID: <7vr4hilt28.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5188B165.3050709@alum.mit.edu> (Michael Haggerty's message of "Tue, 07 May 2013 09:46:45 +0200")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> 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.
Both are intertwined.
I was looking at the history of your project at GitHub. I got an
impression that it is better to evolve as a standalone project with
its own rich history, and the longer I looked at it, the more
convinced I got that I shouldn't pull history from you.
As "batteries included" service for the end users, it may be
convenient to have a copy of a stable release of the script in the
contrib/ area, but I do not think if it is the best for the script
to further develop it in my tree. I'd be just an unnecessary
bottleneck.
I have a mildly strong suspicion that a better approach might be to:
- Copy the current stable snapshot to the contrib/ area, but mark
it clearly that the copy is merely for convenience, meant for end
users who choose not to pull from your authoritative GitHub
repository, and the real development happens elsewhere;
- Keep the development at your GitHub repository, with you as the
project lead. People who are interested in evolving it gather
and work there; and
- Update what is in contrib/ in my tree with a stable snapshot,
every once in a while (close to the release points of Git project
or of MultiMail project).
next prev parent reply other threads:[~2013-05-07 15:15 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
2013-05-07 15:15 ` Junio C Hamano [this message]
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=7vr4hilt28.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=chiestand@salk.edu \
--cc=git@vger.kernel.org \
--cc=mbranchaud@xiplink.com \
--cc=mhagger@alum.mit.edu \
--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 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.