From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Update "If something goes wrong" in Documentation/admin-guide/README.rst
Date: Wed, 13 Jul 2022 13:58:51 -0600 [thread overview]
Message-ID: <87o7xs4wec.fsf@meer.lwn.net> (raw)
In-Reply-To: <1dc0ab09-2cfd-a310-d1da-ef7d3cc47a71@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Maybe just copying the "short guide" from the top of
> reporting-issues.rst might be the most elegant solution for README.rst
> while adding the link your mentioned (maybe while adding a comment to
> reporting-issues.rst saying something like 'if you update this section,
> update the copy over there, too'). But I'm not sure myself right now if
> that's really the best way forward; maybe a few modifications might be
> good here. Let's see what Jonathan says.
Let's not duplicate the text; why not just link over to
reporting-issues.rst?
In general, README.rst has seen little attention for a long time and
could benefit from a major thrashing, methinks.
Thanks,
jon
prev parent reply other threads:[~2022-07-13 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 7:26 Update "If something goes wrong" in Documentation/admin-guide/README.rst Lukas Bulwahn
2022-07-13 9:41 ` Thorsten Leemhuis
2022-07-13 10:06 ` Lukas Bulwahn
2022-07-13 19:58 ` Jonathan Corbet [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=87o7xs4wec.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
/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).