All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst
Date: Thu, 25 Aug 2022 00:39:26 -0700	[thread overview]
Message-ID: <59ae46dd-7fa3-a48f-58cb-a7a58d4e33ab@infradead.org> (raw)
In-Reply-To: <CAKXUXMwLofvhBXqzdoq_q_89jZ8THU0WX=DY+RnCo=PN7QqspA@mail.gmail.com>



On 8/25/22 00:35, Lukas Bulwahn wrote:
> On Thu, Aug 25, 2022 at 5:24 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>>
>>
>> On 8/24/22 01:08, Lukas Bulwahn wrote:
>>> 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.
>>
>> Yeah. And I suspect that scripts/patch-kernel is even more obsolete
>> than applying-patches.rst.
>>
> 
> Randy, would you know if there are still users out there?
> Would it help to replace this script with a minimal script that only
> reports to "Please use git to obtain a recent repository. Update
> versions and apply patches with git in a controlled way.".

I have no idea, but I haven't seen any comments or references about it
in many years. I think it would be safe to remove it, at least on a
trial basis.


> If someone complains, we revert the patch. If no one complains within
> a year or two, we could consider shutting down the infrastructure
> creating those patch archives as well, and delete the documentation
> referring to that.

Yes, something like that is probably in our future.

-- 
~Randy

  reply	other threads:[~2022-08-25  7:39 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 [this message]
2022-08-25  7:53     ` Bagas Sanjaya
2022-08-25 18:48 ` Jonathan Corbet
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=59ae46dd-7fa3-a48f-58cb-a7a58d4e33ab@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bagasdotme@gmail.com \
    --cc=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 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.