From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] docs: reporting-issues: streamline process and solve a FIXME
Date: Thu, 25 Mar 2021 20:37:29 +0100 [thread overview]
Message-ID: <4bc573bf-3dc1-fb6b-e6d7-d51993725c29@leemhuis.info> (raw)
In-Reply-To: <87y2ebysy8.fsf@meer.lwn.net>
On 25.03.21 19:43, Jonathan Corbet wrote:
> Thorsten Leemhuis <linux@leemhuis.info> writes:
>
>> That's why I'd like to speed things up a little. But for that it would
>> be good to have something from you: a kind of "I like the direction
>> where this patch set is heading and I'm optimistic that we get it merged
>> for 5.13-rc1" message from you. With something like that I could move
>> ahead as outlined above already. Do you maybe have a minute for that?
> Honestly, I don't see any reason to delay this work any further, so I've
> just applied the set.
Ahh, great, many thx.
> Sorry for the slowness,
No worries, it's improvements to a docs text, not a crucial security
issue in core code. :-D
> it has been a rather harsh week.
I hope things will get better soon!
BTW, I wondered it it would make sense to add a entry to the MAINTAINERS
file for the text so I can keep and eye on things and help with fine
tuning. Let me known if you think that idea is overblown, otherwise I'll
likely add one with the patch that I'll send sooner or later to remove
the WIP box near the top.
Ciao (and make sure to take care of yourself!), Thorsten
next prev parent reply other threads:[~2021-03-25 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 19:27 [PATCH v3 0/5] docs: reporting-issues: streamline process and solve a FIXME Thorsten Leemhuis
2021-03-19 19:27 ` [PATCH v3 1/5] docs: reporting-issues.rst: fix small typos and style issues Thorsten Leemhuis
2021-03-19 19:27 ` [PATCH v3 2/5] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little Thorsten Leemhuis
2021-03-19 19:27 ` [PATCH v3 3/5] docs: reporting-issues.rst: reorder some steps Thorsten Leemhuis
2021-03-19 19:27 ` [PATCH v3 4/5] docs: reporting-issues.rst: duplicate sections for reviewing purposes Thorsten Leemhuis
2021-03-19 19:27 ` [PATCH v3 5/5] docs: reporting-issues.rst: improved process esp. for stable regressions Thorsten Leemhuis
2021-03-25 12:16 ` [PATCH v3 0/5] docs: reporting-issues: streamline process and solve a FIXME Thorsten Leemhuis
2021-03-25 18:43 ` Jonathan Corbet
2021-03-25 19:37 ` Thorsten Leemhuis [this message]
2021-03-25 19:43 ` Jonathan Corbet
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=4bc573bf-3dc1-fb6b-e6d7-d51993725c29@leemhuis.info \
--to=linux@leemhuis.info \
--cc=corbet@lwn.net \
--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).