From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Workflows <workflows@vger.kernel.org>
Cc: Dante Strock <dantestrock@hotmail.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2] Documentation: process: Arbitrarily bump kernel major version number
Date: Mon, 22 Sep 2025 21:01:18 +0700 [thread overview]
Message-ID: <ff092ff5-8ee1-4e91-b7f7-e5beb1d6d759@gmail.com> (raw)
In-Reply-To: <87h5wu8x7o.fsf@trenco.lwn.net>
On 9/22/25 19:53, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
>> The big picture section of 2.Process.rst currently hardcodes major
>> version number to 5 since fb0e0ffe7fc8e0 ("Documentation: bring process
>> docs up to date"). As it can get outdated when it is actually
>> incremented (the recent is 6 and will be 7 in the near future),
>> arbitrarily bump it to 9, giving a headroom for a decade.
>>
>> Note that the version number examples are kept to illustrate the
>> numbering scheme.
>>
>> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>
> Just FYI, I've pretty much shut docs down for the upcoming merge window.
> I'm probably not the only one.
>
So it is slated for 6.19 then?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-09-22 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:42 [PATCH v2] Documentation: process: Arbitrarily bump kernel major version number Bagas Sanjaya
2025-09-22 12:53 ` Jonathan Corbet
2025-09-22 14:01 ` Bagas Sanjaya [this message]
2025-09-22 14:07 ` Jonathan Corbet
2025-09-22 22:23 ` Bagas Sanjaya
2025-10-14 15:15 ` Jonathan Corbet
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=ff092ff5-8ee1-4e91-b7f7-e5beb1d6d759@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dantestrock@hotmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=workflows@vger.kernel.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