From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: siddharthasthana31@gmail.com, git@vger.kernel.org,
viakliushin@gitlab.com, johncai86@gmail.com
Subject: Re: [PATCH] cat-file: fix mailmap application for different author and committer
Date: Thu, 12 Jun 2025 16:49:23 -0700 [thread overview]
Message-ID: <xmqqecvobjwc.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD1hBo_ZH1nyGBOoQOwx=44CfnkhEOHYu3_XMwSzXQAHdg@mail.gmail.com> (Christian Couder's message of "Wed, 11 Jun 2025 11:38:02 +0200")
Christian Couder <christian.couder@gmail.com> writes:
> On Wed, Jun 11, 2025 at 8:27 AM <siddharthasthana31@gmail.com> wrote:
>
>> Reported-by: Vasilii Iakliushin <viakliushin@gitlab.com>
>> Reviewed-by: Christian Couder <christian.couder@gmail.com>
>
> Nit: I reviewed it when you suggested it on a GitLab MR (Merge
> Request), but I am not sure it counts unless I also review it here. I
> think the "Reviewed-by: ..." trailer is for patches reviewed on the
> regular Git mailing list (or maybe on the private Git security list).
> So maybe "Helped-by: ..." would have been better in this case.
If somebody (including me) sees your reviewed-by on a patch and do
not remember they saw your review here, they might ask, but as long
as you are OK to have your name on the reviewed-by trailer, meaning
you have carefully inspected exactly the same version of the patch
and are willing to stand behind the change, it is perfectly fine.
On the other hand, if you see somebody attach your reviewed-by to a
patch that you didn't review, or is substantially different from the
one you reviewed, please raise a stink about it. I do not think
this case is such a case.
> Anyway I have now reviewed it again and I found it great.
>
> Thanks for working on this!
>
>> Signed-off-by: Siddharth Asthana <siddharthasthana31@gmail.com>
>> ---
Thanks.
next prev parent reply other threads:[~2025-06-12 23:49 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 [this message]
2025-06-11 15:53 ` Junio C Hamano
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=xmqqecvobjwc.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