From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 0/2] Revamp admin-guide/tainted-kernels.rst to make it more comprehensible
Date: Wed, 9 Jan 2019 12:52:44 +0100 [thread overview]
Message-ID: <2ff05fde-089b-a734-b8aa-e676e51fe0b6@leemhuis.info> (raw)
In-Reply-To: <20190108164737.0c2539a6@lwn.net>
Jonathan Corbet schrieb am 09.01.19 um 00:47:
> On Tue, 8 Jan 2019 20:40:05 +0100
> Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
> OK, so we're so close... I think the patches are good; they are a welcome
> improvement to the documentation and the script looks great. Thanks for
> doing this!
More to come, but the revamp for reporting-bugs.rst that I started
already will take a little bit longer to get done, as there is much
ground to cover... (and there are three Linux conferences ahead for me
in the next few weeks, too)
> Patches applied.
thx
> Now for the "I love your patch, something to improve part" :)
> - Patch 1 didn't apply to docs-next; probably you got caught by the
> fast-forward to 5.0-rc1. I've applied it to 4.20 then merged to
> resolve the conflict in tools/Makefile.
Ugh, sorry, rechecking was on my mental todo list, but fell through the
cracks
> - I was tempted to ask you to redo the changelogs, but ended up just
> tweaking them myself.
Thx.
> Changelogs should focus on what the patch does
> and why; they aren't usually the place for the history of how the patch
> came to exist in its current form.
Looks like I got carried away a little bit :-/
> I'll append what actually got
> committed. (Filling to 72 columns or so is also a nice touch for
> changelogs).
Ohh, I thought it was 80. *makesnote*
> [...]
Ciao, Thorsten
prev parent reply other threads:[~2019-01-09 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 19:40 Thorsten Leemhuis
2019-01-08 19:40 ` [PATCH v2 1/2] tools: create tools/debugging/ and add a script decoding /proc/sys/kernel/tainted Thorsten Leemhuis
2019-01-08 19:40 ` [PATCH v2 2/2] docs: Revamp tainted-kernels.rst to make it more comprehensible Thorsten Leemhuis
2019-01-08 23:47 ` [PATCH v2 0/2] Revamp admin-guide/tainted-kernels.rst " Jonathan Corbet
2019-01-09 11:52 ` Thorsten Leemhuis [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=2ff05fde-089b-a734-b8aa-e676e51fe0b6@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
all inboxes | Powered by JetHome®