workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: workflows@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v1] docs: 5.Posting.rst: describe Fixes: and Link: tags
Date: Mon, 3 Jan 2022 13:31:09 +0100	[thread overview]
Message-ID: <b7cc0cd0-887e-fd19-d570-1182ec5e7b14@leemhuis.info> (raw)
In-Reply-To: <7a9999a4-257c-3428-779e-0fdbf02d4782@infradead.org>

Hi Randy! Thx for taking a look. Your helpful feedback made me CC you on
the RFC on a document about regressions I sent today as well. Feel free
to ignore it, if you're not interested.

On 03.01.22 08:36, Randy Dunlap wrote:
> On 1/2/22 23:15, Thorsten Leemhuis wrote:

>> Lo! If there is still a chance I'l like to get this patch into v5.17, as
>                                  I'd
>
>>   Patch itself is unchanged, patch description slighly changed. Might
>                                                  slightly
> 
>>   later submit other changes from that series seperately, too, still
>                                                 separately,

Note to self: avoid last minute changes. :-/

>> ---
>>  Documentation/process/5.Posting.rst | 29 ++++++++++++++++++++++-------
>>  1 file changed, 22 insertions(+), 7 deletions(-)
> [...]
>> +A third kind of tags are used to document who was involved in the development of
>                 of tag is used

Many thx, fixed all of these locally for v2.

Ciao, Thorsten

  reply	other threads:[~2022-01-03 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  7:15 Thorsten Leemhuis
2022-01-03  7:36 ` Randy Dunlap
2022-01-03 12:31   ` Thorsten Leemhuis [this message]
2022-01-03 22:51 ` Jonathan Corbet
2022-01-04 16:58   ` 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=b7cc0cd0-887e-fd19-d570-1182ec5e7b14@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 \
    --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