From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Shobhit Kukreti <shobhitkukreti@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/4] docs: admin-guide: Sort the "unordered guides" to avoid merge conflicts
Date: Tue, 15 Oct 2019 12:38:01 -0600 [thread overview]
Message-ID: <20191015123801.0ba2d123@lwn.net> (raw)
In-Reply-To: <20191012171114.6589-1-j.neuschaefer@gmx.net>
On Sat, 12 Oct 2019 19:11:09 +0200
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
> Since the "unordered guides" linked in admin-guide/index.rst are not
> supposed to be in any particular order, let's sort them alphabetically
> to avoid the risk of merge conflicts by spreading newly added lines more
> evenly.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
I've applied this as being better than nothing, but I would *really* be
pleased if somebody could spend some time imposing a more interesting
order on those unordered guides. Making readers pick through a long list
of random documents isn't all that friendly.
(The rest of the set is applied as well).
Thanks,
jon
prev parent reply other threads:[~2019-10-15 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 17:11 [PATCH RFC 1/4] docs: admin-guide: Sort the "unordered guides" to avoid merge conflicts Jonathan Neuschäfer
2019-10-12 17:11 ` [PATCH 2/4] docs: admin-guide: Move Dell RBU document from driver-api Jonathan Neuschäfer
2019-10-13 6:23 ` Andy Shevchenko
2019-10-12 17:11 ` [PATCH 3/4] docs: admin-guide: dell_rbu: Rework the title Jonathan Neuschäfer
2019-10-12 17:11 ` [PATCH 4/4] docs: admin-guide: dell_rbu: Improve formatting and spelling Jonathan Neuschäfer
2019-10-15 18:38 ` 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=20191015123801.0ba2d123@lwn.net \
--to=corbet@lwn.net \
--cc=j.neuschaefer@gmx.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=shobhitkukreti@gmail.com \
--cc=tglx@linutronix.de \
--cc=willy@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).