git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthieu Moy <git@matthieu-moy.fr>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Michael Haggerty <mhagger@alum.mit.edu>,
	Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH] multimail: stop shipping a copy
Date: Thu, 10 Jun 2021 16:03:04 +0200 (CEST)	[thread overview]
Message-ID: <1554066605.61418500.1623333784687.JavaMail.zimbra@matthieu-moy.fr> (raw)
In-Reply-To: <877dj22fly.fsf@evledraar.gmail.com>

"Ævar Arnfjörð Bjarmason" <avarab@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.

Thanks.

> 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.

Yes. In practice, I am no longer a user of git-multimail.py (my use of Git
moved from some self-hosted repo on a server accessible through SSH to some
more black-box hosting like GitLab where I can't use it anymore), and I
receive very few pull-requests and issues, so the project is essentially
stalled. Not dead, but probably just good enough so no real evolution
happen these days.

> The upstream maintainer(s) are active contributors to git,

Actually, I used to, but it's been a while since I contributed to Git. I've
been busy with other stuff, and I'm struggling to find time to come back.

Michael used to be the maintainer, but completely left the project after I
took it over.

> so the risk of this becoming stale seems low.

This part is still true: sending the patch to Git is part of my release
checklist, I'm unlikely to forget.

That said, the benefit of keeping a copy in git.git is debatable, and
probably low. I have no objection in removing it, i.e. applying Dscho's
patch.

> 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.

I'm all for recommending it in githooks, but this can be done by pointing
to GitHub's URL instead of a local path. Actually the sample script could
look like

# Fetch git-multimail.py from https://github.com/git-multimail/git-multimail/
# adapt and uncomment the following line:
#exec /path/to/git_multimail.py

Cheers,

-- 
Matthieu Moy
https://matthieu-moy.fr/

  reply	other threads:[~2021-06-10 14:23 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
2021-06-10 14:03   ` Matthieu Moy [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1554066605.61418500.1623333784687.JavaMail.zimbra@matthieu-moy.fr \
    --to=git@matthieu-moy.fr \
    --cc=avarab@gmail.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).