From: Todd Zullinger <tmz@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com,
Ariadne Conill <ariadne@dereferenced.org>
Subject: Re: Git for Windows v2.23.0-rc0, was Re: [ANNOUNCE] Git v2.23.0-rc0
Date: Thu, 1 Aug 2019 18:18:58 -0400 [thread overview]
Message-ID: <20190801221858.GN4545@pobox.com> (raw)
In-Reply-To: <xmqq5zngmtzh.fsf@gitster-ct.c.googlers.com>
Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Jeff King <peff@peff.net> writes:
>>
>>>> + if (mailmap < 0)
>>>> mailmap = 0;
>>>> - }
>>>
>>> This should be "mailmap = 1" to match the commit message, no? (Which
>>> also implies we may want a new test).
>>
[...]
> +test_expect_success 'log.mailmap is true by default these days' '
> + git log --author Santa | grep Author >actual &&
> + test_cmp expect actual
> +'
> +
> test_expect_success 'Only grep replaced author with --use-mailmap' '
> git log --use-mailmap --author "<cto@coompany.xx>" >actual &&
> test_must_be_empty actual
With log.mailmap true by default, should we also have some
tests to ensure that --no-use-mailmap and log.mailmap=False
do the right thing? (I mean eventually, not necessarily
with this patch as extra work for you Junio.)
(If I was certain the answer is "yes" and more familiar with
t4203, I would have sent this in diff format.)
--
Todd
next prev parent reply other threads:[~2019-08-01 22:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 21:49 [ANNOUNCE] Git v2.23.0-rc0 Junio C Hamano
2019-07-31 12:43 ` Git for Windows v2.23.0-rc0, was " Johannes Schindelin
2019-07-31 23:18 ` Jeff King
2019-08-01 0:21 ` Jonathan Nieder
2019-08-01 0:37 ` Ariadne Conill
2019-08-01 1:00 ` Jeff King
2019-08-01 1:14 ` Jonathan Nieder
2019-08-01 1:38 ` Ariadne Conill
2019-08-01 2:53 ` Jeff King
2019-08-01 3:21 ` Junio C Hamano
2019-08-01 4:54 ` Ariadne Conill
2019-08-01 21:39 ` Johannes Schindelin
2019-08-01 15:45 ` Junio C Hamano
2019-08-01 16:12 ` Ariadne Conill
2019-08-01 21:36 ` Jeff King
2019-08-01 21:46 ` Junio C Hamano
2019-08-01 21:54 ` Junio C Hamano
2019-08-01 22:18 ` Todd Zullinger [this message]
2019-08-02 2:27 ` Jonathan Nieder
2019-08-02 16:53 ` Junio C Hamano
2019-08-02 18:35 ` Jeff King
2019-08-01 1:04 ` [git-for-windows] " Bryan Turner
2019-08-01 21:40 ` Johannes Schindelin
2019-08-01 14:12 ` [PATCH] RelNotes/2.23.0: fix a few typos and other minor issues Martin Ågren
2019-08-01 15:56 ` Junio C Hamano
2019-08-01 15:57 ` Junio C Hamano
2019-08-01 19:28 ` Martin Ågren
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=20190801221858.GN4545@pobox.com \
--to=tmz@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ariadne@dereferenced.org \
--cc=git-for-windows@googlegroups.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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.