[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1635152553.git.linux@leemhuis.info>
Date: Mon, 25 Oct 2021 11:06:34 +0200
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Jonathan Corbet <corbet@....net>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/1] docs: improve when and how to use Link: tags
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
Powered by blists - more mailing lists