From: Junio C Hamano <gitster@pobox.com>
To: siddharthasthana31@gmail.com
Cc: git@vger.kernel.org, christian.couder@gmail.com,
viakliushin@gitlab.com, johncai86@gmail.com
Subject: Re: [PATCH] cat-file: fix mailmap application for different author and committer
Date: Wed, 11 Jun 2025 08:53:40 -0700 [thread overview]
Message-ID: <xmqqy0tyi8aj.fsf@gitster.g> (raw)
In-Reply-To: <20250611062643.8639-1-siddharthasthana31@gmail.com> (siddharthasthana's message of "Wed, 11 Jun 2025 11:56:43 +0530")
siddharthasthana31@gmail.com writes:
> From: Siddharth Asthana <siddharthasthana31@gmail.com>
>
> The git cat-file command with --mailmap option fails to apply mailmap
> transformations to the committer field when the author and committer
> identities are different. This occurs due to a missing newline handling
> in apply_mailmap_to_header() after processing each identity line.
> ...
> This ensures that all identity headers in commit and tag objects are
> consistently processed regardless of whether the author and committer
> are the same person.
Nicely described.
While the above explains what is wrong in the current code, it does
not tell if that was buggy from the beginning or we unintentionally
broke it. It seems that this logic came from e9c1b0e3 (revision:
improve commit_rewrite_person(), 2022-07-19) when a much simpler
version of commit_rewrite_person() that worked on one "person
header" at a time (as there are only two, author and committer,
anyway) was rewritten to use this function, and it was broken during
the rewrite?
> diff --git a/t/t4203-mailmap.sh b/t/t4203-mailmap.sh
> index 4a6242ff99..98dd0ae12f 100755
> --- a/t/t4203-mailmap.sh
> +++ b/t/t4203-mailmap.sh
> @@ -1133,4 +1133,37 @@ test_expect_success 'git cat-file --batch-command returns correct size with --us
> test_cmp expect actual
> '
>
> +test_expect_success 'git cat-file --mailmap works with different author and committer' '
> + test_when_finished "rm .mailmap" &&
> + cat >.mailmap <<-\EOF &&
> + Mailmapped User <mailmapped-user@gitlab.com> C O Mitter <committer@example.com>
> + EOF
> + git commit --allow-empty -m "different author/committer" \
> + --author="Different Author <different@example.com>" &&
> + cat >expect <<-\EOF &&
> + author Different Author <different@example.com>
> + committer Mailmapped User <mailmapped-user@gitlab.com>
> + EOF
> + git cat-file --mailmap commit HEAD >log &&
> + sed -n "/^author /s/\([^>]*>\).*/\1/p; /^committer /s/\([^>]*>\).*/\1/p" log >actual &&
Perhaps just a matter of taste, but
sed -n -e "/^author /s/>.*/>/p" -e "/^committer /s/>.*/>/p"
may be easier to read and more portable (as some implementation of
sed is picky about semicolon concatenated multiple commands).
> + test_cmp expect actual
> +'
> +
> +test_expect_success 'git cat-file --mailmap maps both author and committer when both need mapping' '
> + test_when_finished "rm .mailmap" &&
> + cat >.mailmap <<-\EOF &&
> + Mapped Author <mapped-author@example.com> <different@example.com>
> + Mapped Committer <mapped-committer@example.com> C O Mitter <committer@example.com>
> + EOF
> + git commit --allow-empty -m "both author and committer mapped" \
> + --author="Different Author <different@example.com>" &&
> + cat >expect <<-\EOF &&
> + author Mapped Author <mapped-author@example.com>
> + committer Mapped Committer <mapped-committer@example.com>
> + EOF
> + git cat-file --mailmap commit HEAD >log &&
> + sed -n "/^author /s/\([^>]*>\).*/\1/p; /^committer /s/\([^>]*>\).*/\1/p" log >actual &&
> + test_cmp expect actual
> +'
> +
> test_done
next prev parent reply other threads:[~2025-06-11 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 6:26 [PATCH] cat-file: fix mailmap application for different author and committer siddharthasthana31
2025-06-11 9:38 ` Christian Couder
2025-06-12 23:49 ` Junio C Hamano
2025-06-11 15:53 ` Junio C Hamano [this message]
2025-06-11 19:05 ` Eric Sunshine
2025-06-11 23:35 ` Junio C Hamano
2025-06-13 9:20 ` Siddharth Asthana
2025-06-13 11:57 ` [PATCH v2] " siddharthasthana31
2025-06-13 12:59 ` Christian Couder
2025-06-13 15:56 ` 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=xmqqy0tyi8aj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=johncai86@gmail.com \
--cc=siddharthasthana31@gmail.com \
--cc=viakliushin@gitlab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox