From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH v1] docs: recommend using Link: whenever using Reported-by:
Date: Thu, 23 Feb 2023 12:49:02 -0700 [thread overview]
Message-ID: <87ttzc40y9.fsf@meer.lwn.net> (raw)
In-Reply-To: <9a07ec640d809723492f8ade4f54705914e80419.1676369564.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Encourage developers to place Link: tag pointing to the report when they
> are using Reported-by: tags. Those links are often extremely useful for
> any code archaeologist that wants to know more about the backstory of a
> change than the commit message provides. That includes maintainers
> higher up in the patch-flow hierarchy, which is why Linus asks
> developers to add such links [1, 2, 3]. To quote [1]:
Applied, thanks.
jon
prev parent reply other threads:[~2023-02-23 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 10:13 Thorsten Leemhuis
2023-02-23 19:49 ` Jonathan Corbet [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=87ttzc40y9.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®