From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>,
linux-doc@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: workflows@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
regressions@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH v4 3/3] docs: reporting-issues.rst: link new document about regressions
Date: Tue, 01 Feb 2022 16:23:57 -0700 [thread overview]
Message-ID: <87bkzq5fxu.fsf@meer.lwn.net> (raw)
In-Reply-To: <978ad91647e93b20b7fe12c3f237f6de8f9eaca1.1643710947.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Make Documentation/admin-guide/reporting-issues.rst point to the newly
> created document about regressions
> (Documentation/admin-guide/regressions-users.rst). This allows to
> shorten a few explanations the new document describes better and in more
> detail.
>
> While at it move the copyright hint to the end of the file, as suggested
> during review of the new documents about regressions.
>
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
> .../admin-guide/reporting-issues.rst | 60 +++++++++----------
> 1 file changed, 29 insertions(+), 31 deletions(-)
[...]
> +You deal with a regression if some application or practical use case running
> +fine with one Linux kernel works worse or not at all with a newer version
> +compiled using a similar configuration. The document
> +'Documentation/admin-guide/regressions-users.rst' explains this in more detail.
Some of those quotes around file names are still sneaking in.
Thanks,
jon
next prev parent reply other threads:[~2022-02-01 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 10:26 [PATCH v4 0/3] docs: add two texts covering regressions Thorsten Leemhuis
2022-02-01 10:26 ` [PATCH v4 1/3] docs: add two documents about regression handling Thorsten Leemhuis
2022-02-01 23:13 ` Jonathan Corbet
2022-02-02 10:05 ` Thorsten Leemhuis
2022-02-15 18:49 ` Thorsten Leemhuis
2022-02-01 10:26 ` [PATCH v4 2/3] docs: regressions*rst: rules of thumb for handling regressions Thorsten Leemhuis
2022-02-01 23:21 ` Jonathan Corbet
2022-02-02 9:47 ` Thorsten Leemhuis
2022-02-01 10:26 ` [PATCH v4 3/3] docs: reporting-issues.rst: link new document about regressions Thorsten Leemhuis
2022-02-01 23:23 ` Jonathan Corbet [this message]
2022-02-02 6:08 ` 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=87bkzq5fxu.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.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 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.