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 v1 0/2] Prefer lore.kernel.org and explain Link: tags better
Date: Thu, 7 Oct 2021 10:04:59 +0200 [thread overview]
Message-ID: <cover.1633593385.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 missed
the modified section myself at first, as I simply grepped for 'Link:'
and only found an explanation in configure-git.rst.
Konstantin after posting v1 suggested to use lore.kernel.org instead or
lkml.kernel.org, which made me add a patch to realize this everywhere in
the docs.
v2:
- 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
Ciao, Thorsten
Thorsten Leemhuis (2):
docs: use the lore redirector everywhere
docs: submitting-patches: make section about the Link: tag more
explicit
Documentation/asm-annotations.rst | 2 +-
.../kbuild/Kconfig.recursion-issue-02 | 2 +-
Documentation/maintainer/pull-requests.rst | 2 +-
Documentation/networking/msg_zerocopy.rst | 2 +-
Documentation/process/maintainer-tip.rst | 4 +--
Documentation/process/submitting-patches.rst | 34 ++++++++++++-------
.../it_IT/process/submitting-patches.rst | 4 +--
.../zh_CN/maintainer/pull-requests.rst | 2 +-
.../zh_CN/process/submitting-patches.rst | 4 +--
.../zh_TW/process/submitting-patches.rst | 4 +--
Documentation/x86/entry_64.rst | 2 +-
Documentation/x86/orc-unwinder.rst | 4 +--
12 files changed, 38 insertions(+), 28 deletions(-)
base-commit: b19511926cb50d59c57189739d03c21df325710f
--
2.31.1
next reply other threads:[~2021-10-07 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 8:04 Thorsten Leemhuis [this message]
2021-10-07 8:05 ` [PATCH v1 1/2] docs: use the lore redirector everywhere Thorsten Leemhuis
2021-10-07 8:05 ` [PATCH v1 2/2] docs: submitting-patches: make section about the Link: tag more explicit Thorsten Leemhuis
2021-10-07 9:31 ` Jani Nikula
2021-10-08 9:47 ` Thorsten Leemhuis
2021-10-21 8:44 ` Thorsten Leemhuis
2021-10-21 9:43 ` Jani Nikula
2021-10-07 13:53 ` [PATCH v1 0/2] Prefer lore.kernel.org and explain Link: tags better Konstantin Ryabitsev
2021-10-12 20:03 ` Jonathan Corbet
2021-10-13 4:37 ` 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.1633593385.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).