From: Jonathan Corbet <corbet@lwn.net>
To: Theodore Ts'o <tytso@mit.edu>, Greg KH <gregkh@linuxfoundation.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Outreachy <outreachy@lists.linux.dev>,
Thorsten Leemhuis <linux@leemhuis.info>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Akira Yokosawa <akiyks@gmail.com>,
Alison Schofield <alison.schofield@intel.com>,
Kloudifold <cloudifold.3125@gmail.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH] Documentation: submitting-patches: Disqualify style fixes from Fixes: tag
Date: Thu, 16 Mar 2023 09:01:41 -0600 [thread overview]
Message-ID: <87zg8cn3je.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230316145503.GN860405@mit.edu>
"Theodore Ts'o" <tytso@mit.edu> writes:
> On Thu, Mar 16, 2023 at 09:26:21AM +0100, Greg KH wrote:
>> > Coding style is not a bug, but that's obvious.
>>
>> I agree, let's not make this file even longer than it is if at all
>> possible.
>>
>
> I've actually been wondering if there is some way to split the file
> since it's quite large already. It's been unclear to me whether that
> would make it easier or harder to find stuff though. :-/
I made a pass over it a few years ago and managed to shorten it a fair
amount, but it clearly still needs attention. This is one of our most
important and heavily referenced documents, and it would be nice if
newcomers didn't feel like they were being asked to read a version of
War and Peace written by Kafka before they can contribute.
I'll try to find time to think about this some.
jon
next prev parent reply other threads:[~2023-03-16 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 8:20 Bagas Sanjaya
2023-03-16 8:23 ` Krzysztof Kozlowski
2023-03-16 8:26 ` Greg KH
2023-03-16 14:55 ` Theodore Ts'o
2023-03-16 15:01 ` Jonathan Corbet [this message]
2023-03-17 7:53 ` Bagas Sanjaya
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=87zg8cn3je.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=alison.schofield@intel.com \
--cc=bagasdotme@gmail.com \
--cc=cloudifold.3125@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=outreachy@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=tytso@mit.edu \
/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®