From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst
Date: Thu, 25 Aug 2022 12:48:39 -0600 [thread overview]
Message-ID: <87a67syxa0.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220824080836.23087-1-lukas.bulwahn@gmail.com>
Lukas Bulwahn <lukas.bulwahn@gmail.com> writes:
> A quick 'grep "5\.x" . -R' on Documentation shows that README.rst,
> 2.Process.rst and applying-patches.rst all mention the version number "5.x"
> for kernel releases.
>
> As the next release will be version 6.0, updating the version number to 6.x
> in README.rst seems reasonable.
>
> The description in 2.Process.rst is just a description of recent kernel
> releases, it was last updated in the beginning of 2020, and can be
> revisited at any time on a regular basis, independent of changing the
> version number from 5 to 6. So, there is no need to update this document
> now when transitioning from 5.x to 6.x numbering.
>
> The document applying-patches.rst is probably obsolete for most users
> anyway, a reader will sufficiently well understand the steps, even it
> mentions version 5 rather than version 6. So, do not update that to a
> version 6.x numbering scheme.
>
> Update version number from 5.x to 6.x in README.rst only.
I've gone ahead and applied this.
For the other files:
- I don't think 2.Process.rst needs any immediate attention. We could
change the wording from "recent release history" to "The release
history in early 2022 looked like:" or something like that. There is
no reason why it has to be the latest releases.
- applying-patches.rst should just go. I didn't prevail last time I
tried to make that point, but I still don't think that we help
anybody by dragging 1990's instructions around now.
Thanks,
jon
next prev parent reply other threads:[~2022-08-25 18:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 8:08 [PATCH] docs: Update version number from 5.x to 6.x in README.rst Lukas Bulwahn
2022-08-25 3:08 ` Bagas Sanjaya
2022-08-25 7:27 ` Lukas Bulwahn
2022-08-25 3:24 ` Randy Dunlap
2022-08-25 7:35 ` Lukas Bulwahn
2022-08-25 7:39 ` Randy Dunlap
2022-08-25 7:53 ` Bagas Sanjaya
2022-08-25 18:48 ` Jonathan Corbet [this message]
2022-08-26 2:19 ` Bagas Sanjaya
2022-08-26 2:24 ` Randy Dunlap
2022-08-26 13:18 ` Jonathan Corbet
2022-08-26 8:28 ` 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=87a67syxa0.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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).