From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] multimail: stop shipping a copy
Date: Thu, 10 Jun 2021 12:31:30 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2106101230340.57@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <pull.977.git.1623313765122.gitgitgadget@gmail.com>
Hi,
On Thu, 10 Jun 2021, Johannes Schindelin via GitGitGadget wrote:
> contrib/hooks/multimail/README.Git | 12 +-
I should point out that this could easily get lost between all those
deleted files... The diff looks like this:
> diff --git a/contrib/hooks/multimail/README.Git b/contrib/hooks/multimail/README.Git
> index 044444245d09..c427efc7bd8e 100644
> --- a/contrib/hooks/multimail/README.Git
> +++ b/contrib/hooks/multimail/README.Git
> @@ -1,15 +1,7 @@
> -This copy of git-multimail is distributed as part of the "contrib"
> -section of the Git project as a convenience to Git users.
> git-multimail is developed as an independent project at the following
> website:
>
> https://github.com/git-multimail/git-multimail
>
> -The version in this directory was obtained from the upstream project
> -on January 07 2019 and consists of the "git-multimail" subdirectory from
> -revision
> -
> - 04e80e6c40be465cc62b6c246f0fcb8fd2cfd454 refs/tags/1.5.0
> -
> -Please see the README file in this directory for information about how
> -to report bugs or contribute to git-multimail.
> +Please refer to that project page for information about how to report
> +bugs or contribute to git-multimail.
Ciao,
Dscho
next prev parent reply other threads:[~2021-06-10 10:31 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 [this message]
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=nycvar.QRO.7.76.6.2106101230340.57@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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.