From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: CB Bailey <cb@hashpling.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] shortlog: pass the mailmap into the revision walker
Date: Wed, 12 Dec 2018 19:31:33 +0100 [thread overview]
Message-ID: <87va3ymwai.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20181212171052.13415-1-cb@hashpling.org>
On Wed, Dec 12 2018, CB Bailey wrote:
> From: CB Bailey <cbailey32@bloomberg.net>
>
> shortlog always respects the mailmap in its output. Pass the mailmap
> into the revision walker to allow the mailmap to be used with revision
> limiting options such as '--author'.
>
> This removes some apparently inconsistent behaviors when using
> '--author', such as not finding some or all commits for a given author
> which do appear under that author in an unrestricted invocation of
> shortlog or commits being summarized under a different author than the
> specified author.
>
> Signed-off-by: CB Bailey <cbailey32@bloomberg.net>
> ---
>
> Resending with omitted s-o-b.
>
> builtin/shortlog.c | 2 ++
> t/t4203-mailmap.sh | 28 ++++++++++++++++++++++++++++
> 2 files changed, 30 insertions(+)
>
> diff --git a/builtin/shortlog.c b/builtin/shortlog.c
> index 88f88e97b2..a6fb00ade8 100644
> --- a/builtin/shortlog.c
> +++ b/builtin/shortlog.c
> @@ -188,6 +188,8 @@ static void get_from_rev(struct rev_info *rev, struct shortlog *log)
> {
> struct commit *commit;
>
> + rev->mailmap = &log->mailmap;
> +
> if (prepare_revision_walk(rev))
> die(_("revision walk setup failed"));
> while ((commit = get_revision(rev)) != NULL)
> diff --git a/t/t4203-mailmap.sh b/t/t4203-mailmap.sh
> index 43b1522ea2..9bee35b06c 100755
> --- a/t/t4203-mailmap.sh
> +++ b/t/t4203-mailmap.sh
> @@ -383,6 +383,34 @@ test_expect_success 'Shortlog output (complex mapping)' '
>
> '
>
> +test_expect_success 'Shortlog output (complex mapping, filtered)' '
> +
> + printf " 1\tA U Thor <author@example.com>\n" >expect &&
> +
> + git shortlog -es --author="A U Thor" HEAD >actual &&
> + test_cmp expect actual &&
> +
> + printf " 1\tCTO <cto@company.xx>\n" >expect &&
> +
> + git shortlog -es --author=CTO HEAD >actual &&
> + test_cmp expect actual &&
> +
> + printf " 2\tOther Author <other@author.xx>\n" >expect &&
> +
> + git shortlog -es --author="Other Author" HEAD >actual &&
> + test_cmp expect actual &&
> +
> + printf " 2\tSanta Claus <santa.claus@northpole.xx>\n" >expect &&
> +
> + git shortlog -es --author="Santa Claus" HEAD >actual &&
> + test_cmp expect actual &&
> +
> + printf " 1\tSome Dude <some@dude.xx>\n" >expect &&
> +
> + git shortlog -es --author="Some Dude" HEAD >actual &&
> + test_cmp expect actual
> +'
> +
> # git log with --pretty format which uses the name and email mailmap placemarkers
> cat >expect <<\EOF
> Author CTO <cto@coompany.xx> maps to CTO <cto@company.xx>
Makes sense. Not saying this is how it should be, just an equivalently
working patch that I came up with on top while poing at this:
diff --git a/builtin/shortlog.c b/builtin/shortlog.c
index a6fb00ade8..ad84d70d07 100644
--- a/builtin/shortlog.c
+++ b/builtin/shortlog.c
@@ -188,10 +188,9 @@ static void get_from_rev(struct rev_info *rev, struct shortlog *log)
{
struct commit *commit;
- rev->mailmap = &log->mailmap;
-
if (prepare_revision_walk(rev))
die(_("revision walk setup failed"));
+ rev->mailmap = &log->mailmap;
while ((commit = get_revision(rev)) != NULL)
shortlog_add_commit(log, commit);
}
diff --git a/t/t4203-mailmap.sh b/t/t4203-mailmap.sh
index 9bee35b06c..74a269052d 100755
--- a/t/t4203-mailmap.sh
+++ b/t/t4203-mailmap.sh
@@ -384,17 +384,6 @@ test_expect_success 'Shortlog output (complex mapping)' '
'
test_expect_success 'Shortlog output (complex mapping, filtered)' '
-
- printf " 1\tA U Thor <author@example.com>\n" >expect &&
-
- git shortlog -es --author="A U Thor" HEAD >actual &&
- test_cmp expect actual &&
-
- printf " 1\tCTO <cto@company.xx>\n" >expect &&
-
- git shortlog -es --author=CTO HEAD >actual &&
- test_cmp expect actual &&
-
printf " 2\tOther Author <other@author.xx>\n" >expect &&
git shortlog -es --author="Other Author" HEAD >actual &&
I.e. we just need the assignment after prepare_revision_walk() and the
first 2x tests were things that passed before this change.
So that's not a "let's squash that on top" but "I was poking at this and
here's stuff that I fiddled with or surprised me slightly".
next prev parent reply other threads:[~2018-12-12 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 16:41 [PATCH] shortlog: pass the mailmap into the revision walker CB Bailey
2018-12-12 17:10 ` CB Bailey
2018-12-12 18:31 ` Ævar Arnfjörð Bjarmason [this message]
2018-12-12 19:19 ` 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=87va3ymwai.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=cb@hashpling.org \
--cc=git@vger.kernel.org \
/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).