From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Prefer lore.kernel.org and explain Link: tags better
Date: Tue, 12 Oct 2021 14:03:27 -0600 [thread overview]
Message-ID: <875yu2ui28.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1633593385.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> 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
OK, I've applied this one, thanks.
> docs: submitting-patches: make section about the Link: tag more
> explicit
There was a comment on this one, so I've not (yet) applied it.
FWIW, I, too, have the Link: tags put in automatically when I apply a
patch, as Jani described; it's a simple hook in
.git/hooks/applypatch-msg. That seems worth mentioning here more than
instructions on how to construct the link - I doubt many people do it
manually.
Thanks,
jon
next prev parent reply other threads:[~2021-10-12 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 8:04 [PATCH v1 0/2] Prefer lore.kernel.org and explain Link: tags better Thorsten Leemhuis
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 [this message]
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=875yu2ui28.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--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 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.