From: Denton Liu <liu.denton@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.25.0
Date: Wed, 15 Jan 2020 10:42:39 -0500 [thread overview]
Message-ID: <20200115154239.GA40131@generichostname> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2001142258130.46@tvgsbejvaqbjf.bet>
On Tue, Jan 14, 2020 at 10:58:58PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 13 Jan 2020, Denton Liu wrote:
>
> > 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.
>
> Please note that 4c6c7971e0e42f0f1ce7e9472bc3aec8e0c96650 unfortunately
> has the same problem (albeit with Stolee as author), and it already made
> it into `next`.
Since 'next' is getting rewound in a little bit, can we requeue Stolee's
patch with the authorship corrected? Or would it make more sense to
submit a .mailmap patch on top?
Thanks,
Denton
next prev parent reply other threads:[~2020-01-15 15:42 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
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 [this message]
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=20200115154239.GA40131@generichostname \
--to=liu.denton@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).