From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/1] docs: improve when and how to use Link: tags
Date: Mon, 25 Oct 2021 11:06:34 +0200 [thread overview]
Message-ID: <cover.1635152553.git.linux@leemhuis.info> (raw)
Lo! The regression tracking bot I'm working on can automatically mark an
entry as resolved, if the commit message of the fix uses a 'Link' tag to
the report. Many developers already place them, but it afaics would
improve matters to make this more explicit. Especially as I had trouble
finding the explanation myself at first, as I simply grepped for 'Link:'
and only found an explanation in configure-git.rst. But that only covers
how maintainers should use it to make git automatically add links to the
patch review in the archives.
v3:
- drop the first patch (merged)
- slightly improve the text again due to the questions raised during the
review (that's also why I didn't pick up Konstantin's 'reviewed-by' on
v2) and something Linus meanwhile said coincidentally
v2: https://lore.kernel.org/r/cover.1633593385.git.linux@leemhuis.info/
- slightly reword after suggestiones from Konstantin (thx!)
- make this a patch series with an preparatory patch that does
s!lkml.kernel.org!lore.kernel.org! everywhere in the docs
v1: https://lore.kernel.org/r/7dff33afec555fed0bf033c910ca59f9f19f22f1.1633537634.git.linux@leemhuis.info/
- initial version
Thorsten Leemhuis (1):
docs: submitting-patches: make section about the Link: tag more
explicit
Documentation/process/submitting-patches.rst | 33 +++++++++++++-------
1 file changed, 22 insertions(+), 11 deletions(-)
base-commit: 2df9f7f57905e61cf638284bf86af30f7849ed6b
--
2.31.1
next reply other threads:[~2021-10-25 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 9:06 Thorsten Leemhuis [this message]
2021-10-25 9:06 ` [PATCH v3 1/1] docs: submitting-patches: make section about the Link: tag more explicit Thorsten Leemhuis
2021-10-25 21:05 ` Konstantin Ryabitsev
2021-10-26 15:49 ` Jonathan Corbet
2021-10-26 16:45 ` Thorsten Leemhuis
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=cover.1635152553.git.linux@leemhuis.info \
--to=linux@leemhuis.info \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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).