From: Andrew Kreimer <algonell@gmail.com>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] t: fix typos
Date: Fri, 25 Oct 2024 12:20:15 +0300 [thread overview]
Message-ID: <Zxtiz-h7m5YF4Q2N@void.void> (raw)
In-Reply-To: <35e4259a-d442-4b8f-a986-412e04a64770@app.fastmail.com>
On Thu, Oct 24, 2024 at 07:07:00PM +0200, Kristoffer Haugsbakk wrote:
> Just for future series, I think crediting people in the commit message
> for minor review work is overkill. “Reported-by” in particular is often
> used for something more substantial like finding a bug.
>
> That’s my impression anyway, mainly from reading this list.
>
> --
> Kristoffer Haugsbakk
Noted, thank you.
prev parent reply other threads:[~2024-10-25 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 17:01 [PATCH] t: fix typos Andrew Kreimer
2024-10-23 18:00 ` Kristoffer Haugsbakk
2024-10-23 18:33 ` Taylor Blau
2024-10-24 11:44 ` Andrew Kreimer
2024-10-24 11:47 ` [PATCH v2] " Andrew Kreimer
2024-10-24 16:46 ` Taylor Blau
2024-10-24 17:07 ` Kristoffer Haugsbakk
2024-10-25 9:20 ` Andrew Kreimer [this message]
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=Zxtiz-h7m5YF4Q2N@void.void \
--to=algonell@gmail.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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;
as well as URLs for NNTP newsgroup(s).