From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten")
Date: Tue, 8 Dec 2020 10:44:45 -0700 [thread overview]
Message-ID: <20201208104445.0f82ae78@lwn.net> (raw)
In-Reply-To: <cover.1607063223.git.linux@leemhuis.info>
On Fri, 4 Dec 2020 07:43:47 +0100
Thorsten Leemhuis <linux@leemhuis.info> wrote:
> This series adds a new and mostly finished document describing how to report
> issues with the Linux kernel to its developers.
OK, I have applied this series. Thanks to Thorsten for doing all of this
work and sticking with it, and thanks to the others (especially Randy) who
have spent a lot of time reviewing this work.
jon
next prev parent reply other threads:[~2020-12-08 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 6:43 [PATCH v4 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten") Thorsten Leemhuis
2020-12-04 6:43 ` [PATCH v4 1/3] LICENSES: Add the CC-BY-4.0 license Thorsten Leemhuis
2020-12-04 12:23 ` Greg Kroah-Hartman
2020-12-04 21:26 ` Jonathan Corbet
2020-12-04 6:43 ` [PATCH v4 2/3] docs: Add a new text describing how to report bugs Thorsten Leemhuis
2020-12-04 6:43 ` [PATCH v4 3/3] docs: make reporting-bugs.rst obsolete Thorsten Leemhuis
2020-12-08 17:44 ` Jonathan Corbet [this message]
2020-12-09 5:25 ` [PATCH v4 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten") 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=20201208104445.0f82ae78@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=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
/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.