From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
Cc: "Josh Soref" <gitgitgadget@gmail.com>,
git@vger.kernel.org, spectral <spectral@google.com>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] MyFirstContribution: update mailing list sub steps
Date: Sat, 20 Jan 2024 10:08:30 -0800 [thread overview]
Message-ID: <xmqq7ck3g9nl.fsf@gitster.g> (raw)
In-Reply-To: <527ae359-32e7-4c49-b733-614f17876f14@app.fastmail.com> (Kristoffer Haugsbakk's message of "Sat, 20 Jan 2024 11:48:38 +0100")
"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:
> Just curious. What’s the difference between `Reported-by` and
> `Noticed-by`? `Reported-by` is documented in `SubmittingPatches` but not
> the other one. Is perhaps `Reported-by` specifically meant for bug
> reports?
It should be reported-by as the recent trend is to dedup similar
ones without much meaningful distinction and stick to those that are
listed in the document. It was just me being careless and picked
one that used to be relatively common without even thinking:
$ git rev-list --since 1.year --grep=Noticed-by: --count master
2
$ git rev-list --since 1.year --grep=Reported-by: --count master
54
$ git rev-list --since 5.year --until 4.year --grep=Noticed-by: --count master
4
$ git rev-list --since 5.year --until 4.year --grep=Reported-by: --count master
102
$ git rev-list --since 10.year --until 9.year --grep=Noticed-by: --count master
12
$ git rev-list --since 10.year --until 9.year --grep=Reported-by: --count master
54
There probably is a subtle difference perceived between the two by
those who used noticed-by over the years and I think you guessed
their intention right.
prev parent reply other threads:[~2024-01-20 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 20:59 [PATCH] MyFirstContribution: update mailing list sub steps spectral via GitGitGadget
2024-01-19 21:06 ` Konstantin Ryabitsev
2024-01-19 22:26 ` Junio C Hamano
2024-01-19 22:46 ` Kyle Lippincott
2024-01-20 10:48 ` Kristoffer Haugsbakk
2024-01-20 18:08 ` Junio C Hamano [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=xmqq7ck3g9nl.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=spectral@google.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 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.