From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>,
Matthieu Moy <git@matthieu-moy.fr>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] multimail: stop shipping a copy
Date: Fri, 11 Jun 2021 01:00:25 +0900 [thread overview]
Message-ID: <xmqqbl8demli.fsf@gitster.g> (raw)
In-Reply-To: pull.977.git.1623313765122.gitgitgadget@gmail.com
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> 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.
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
FWIW, the upstream hasn't seen any activity since early November
2019. I'm pinging Matthieu just in case, but I do not expect
anybody would object this move.
The fewer files we need to worry about, the better ;-)
> Stop shipping a (potentially stale) copy of multimail
>
> The project is maintained elsewhere.
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-977%2Fdscho%2Fstub-out-contrib-multimail-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-977/dscho/stub-out-contrib-multimail-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/977
>
> contrib/hooks/multimail/CHANGES | 285 --
> contrib/hooks/multimail/CONTRIBUTING.rst | 60 -
> contrib/hooks/multimail/README.Git | 12 +-
> .../README.migrate-from-post-receive-email | 145 -
> contrib/hooks/multimail/README.rst | 774 ---
> .../multimail/doc/customizing-emails.rst | 56 -
> contrib/hooks/multimail/doc/gerrit.rst | 56 -
> contrib/hooks/multimail/doc/gitolite.rst | 118 -
> .../hooks/multimail/doc/troubleshooting.rst | 78 -
> contrib/hooks/multimail/git_multimail.py | 4346 -----------------
> .../hooks/multimail/migrate-mailhook-config | 274 --
> contrib/hooks/multimail/post-receive.example | 101 -
> 12 files changed, 2 insertions(+), 6303 deletions(-)
> delete mode 100644 contrib/hooks/multimail/CHANGES
> delete mode 100644 contrib/hooks/multimail/CONTRIBUTING.rst
> delete mode 100644 contrib/hooks/multimail/README.migrate-from-post-receive-email
> delete mode 100644 contrib/hooks/multimail/README.rst
> delete mode 100644 contrib/hooks/multimail/doc/customizing-emails.rst
> delete mode 100644 contrib/hooks/multimail/doc/gerrit.rst
> delete mode 100644 contrib/hooks/multimail/doc/gitolite.rst
> delete mode 100644 contrib/hooks/multimail/doc/troubleshooting.rst
> delete mode 100755 contrib/hooks/multimail/git_multimail.py
> delete mode 100755 contrib/hooks/multimail/migrate-mailhook-config
> delete mode 100755 contrib/hooks/multimail/post-receive.example
prev parent reply other threads:[~2021-06-10 16:00 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
2021-06-10 15:40 ` Elijah Newren
2021-06-10 10:31 ` Johannes Schindelin
2021-06-10 16:00 ` Junio C Hamano [this message]
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=xmqqbl8demli.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@matthieu-moy.fr \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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).