From: Denton Liu <liu.denton@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [ANNOUNCE] Git v2.25.0
Date: Mon, 13 Jan 2020 21:49:38 -0500 [thread overview]
Message-ID: <20200114024938.GA17003@generichostname> (raw)
In-Reply-To: <xmqqtv4zjgv5.fsf@gitster-ct.c.googlers.com>
On Mon, Jan 13, 2020 at 11:28:30AM -0800, Junio C Hamano wrote:
> New contributors whose contributions weren't in v2.24.0 are as follows.
> Welcome to the Git development community!
>
> Ben Keene, Colin Stolley, Dominic Jäger, Erik Chen, Hariom
> Verma, Heba Waly, James Coglan, James Shubin, Johannes Schindelin
I was quite surprised to see Dscho's name in here until I realised that
this was just erroneous authorship information. Below is a mailmap patch
to fix this.
> via GitGitGadget, Jonathan Gilbert, Josh Holland, Kazuhiro
> Kato, Łukasz Niemier, Manish Goregaokar, Matthew Rogers,
> Mihail Atanassov, Miriam Rubio, Nathan Stocks, Naveen Nathan,
> Nika Layzell, pan93412, Paul Menzel, Philippe Blain, Prarit
> Bhargava, r.burenkov, Ruud van Asseldonk, ryenus, Slavica
> Đukić, Thomas Menzel, Utsav Shah, Yi-Jyun Pan, and Zoli Szabó.
-- >8 --
Subject: [PATCH] .mailmap: fix erroneous authorship for Johannes Schindelin
In 49e268e23e (mingw: safeguard better against backslashes in file
names, 2020-01-09), the commit author is listed as
"Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>", which
is erroneous. Fix the authorship by mapping the erroneous authorship to
his canonical authorship information.
Signed-off-by: Denton Liu <liu.denton@gmail.com>
---
.mailmap | 1 +
1 file changed, 1 insertion(+)
diff --git a/.mailmap b/.mailmap
index 7c9441837a..fbef813f24 100644
--- a/.mailmap
+++ b/.mailmap
@@ -109,6 +109,7 @@ Jim Meyering <jim@meyering.net> <meyering@redhat.com>
Joachim Berdal Haga <cjhaga@fys.uio.no>
Joachim Jablon <joachim.jablon@people-doc.com> <ewjoachim@gmail.com>
Johannes Schindelin <Johannes.Schindelin@gmx.de> <johannes.schindelin@gmx.de>
+Johannes Schindelin <Johannes.Schindelin@gmx.de> Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Johannes Sixt <j6t@kdbg.org> <J.Sixt@eudaptics.com>
Johannes Sixt <j6t@kdbg.org> <j.sixt@viscovery.net>
Johannes Sixt <j6t@kdbg.org> <johannes.sixt@telecom.at>
--
2.25.0.rc1.180.g49a268d3eb
next prev parent reply other threads:[~2020-01-14 2:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 19:28 [ANNOUNCE] Git v2.25.0 Junio C Hamano
2020-01-13 20:13 ` [ANNOUNCE] git-filter-repo v2.25.0 (Was Re: [ANNOUNCE] Git v2.25.0) Elijah Newren
2020-01-13 20:47 ` [ANNOUNCE] Git v2.25.0 Taylor Blau
2020-01-14 2:49 ` Denton Liu [this message]
2020-01-14 3:23 ` [PATCH] .mailmap: map Yi-Jyun Pan's email Denton Liu
2020-01-30 18:24 ` Junio C Hamano
2020-01-14 21:50 ` [ANNOUNCE] Git v2.25.0 Johannes Schindelin
2020-01-14 21:58 ` Johannes Schindelin
2020-01-15 15:42 ` Denton Liu
2020-01-15 18:34 ` 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=20200114024938.GA17003@generichostname \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).