From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Matthieu Moy <git@matthieu-moy.fr>,
Michael Haggerty <mhagger@alum.mit.edu>,
Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH] multimail: stop shipping a copy
Date: Thu, 10 Jun 2021 12:04:52 +0200 [thread overview]
Message-ID: <877dj22fly.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <pull.977.git.1623313765122.gitgitgadget@gmail.com>
On Thu, Jun 10 2021, Johannes Schindelin via GitGitGadget wrote:
> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> The multimail project is developed independently and has its own project
> page. Traditionally, we shipped a copy in contrib/.
>
> However, such a copy is prone to become stale, and users are much better
> served to be directed to the actual project instead.
Let's CC its maintainer / other people who've actively contributed to
it. I've taken the liberty to do that.
It seems to me that the state is that we're on the 1.5.0 release, and
upstream hasn't cut a new release. The upstream maintainer(s) are active
contributors to git, so the risk of this becoming stale seems low.
Having written a system in the past that made use of git-multimail.py
(and sourced it from git.git's copy) I'd think a better direction would
be to keep this and modify githooks(5) to actively recommend it over the
older and less featureful post-receive-email script.
Sure, people can also just get it from github, but to the extent that we
ship any sample/default hooks at all let's start with the one that we'd
recommend using against in favor of git_multimail.py for anything new.
next prev parent reply other threads:[~2021-06-10 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:29 [PATCH] multimail: stop shipping a copy Johannes Schindelin via GitGitGadget
2021-06-10 10:04 ` Ævar Arnfjörð Bjarmason [this message]
2021-06-10 14:03 ` Matthieu Moy
2021-06-10 15:40 ` Elijah Newren
2021-06-10 10:31 ` Johannes Schindelin
2021-06-10 16:00 ` Junio C Hamano
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=877dj22fly.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@matthieu-moy.fr \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=mhagger@alum.mit.edu \
--cc=newren@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.