From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: workflows@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH v1] docs: 5.Posting.rst: describe Fixes: and Link: tags
Date: Tue, 4 Jan 2022 17:58:18 +0100 [thread overview]
Message-ID: <bd81b15d-2da2-8f79-0372-ca9df9f00361@leemhuis.info> (raw)
In-Reply-To: <87ilv0xwjn.fsf@meer.lwn.net>
On 03.01.22 23:51, Jonathan Corbet wrote:
> Thorsten Leemhuis <linux@leemhuis.info> writes:
>
>> Explain Fixes: and Link: tags in Documentation/process/5.Posting.rst,
>> which are missing in this file for unknown reasons and only described in
>> Documentation/process/submitting-patches.rst.
>>
>> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
>> CC: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
>> ---
>> Lo! If there is still a chance I'l like to get this patch into v5.17, as
>
> I think that should be possible. Send me a version with Randy's
> comments addressed; I also had one nit below...
Sounds good. Comments and nit addressed and sent out again:
https://lore.kernel.org/linux-doc/c4a5f5e25fa84b26fd383bba6eafde4ab57c9de7.1641314856.git.linux@leemhuis.info/
Ciao, Thorsten
prev parent reply other threads:[~2022-01-04 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 7:15 [PATCH v1] docs: 5.Posting.rst: describe Fixes: and Link: tags Thorsten Leemhuis
2022-01-03 7:36 ` Randy Dunlap
2022-01-03 12:31 ` Thorsten Leemhuis
2022-01-03 22:51 ` Jonathan Corbet
2022-01-04 16:58 ` Thorsten Leemhuis [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=bd81b15d-2da2-8f79-0372-ca9df9f00361@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=workflows@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).