From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst
Date: Fri, 26 Aug 2022 07:18:04 -0600 [thread overview]
Message-ID: <87fshjw3cj.fsf@meer.lwn.net> (raw)
In-Reply-To: <YwgtoiKl5Azt7Pre@debian.me>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> On Thu, Aug 25, 2022 at 12:48:39PM -0600, Jonathan Corbet wrote:
>> - 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.
>>
>
> Hi jon,
>
> If we're about to rm applying-patches.rst, at least we also need to add
> a warning to the doc, saying "This documentation is obsolete and will be
> removed in the future.", while adding the same deprecation message on
> scripts/patch-kernel. The script can still be usable and kept around for
> a cycle. If no users complain, we will go ahead rm-ing.
A document isn't an API, it's not like users need time to somehow
migrate away from it. If people will be affected by the removal of a
document, we probably shouldn't remove it. The situation here is that
nobody is likely to care. *Somebody* is probably still updating their
kernel with patches somewhere, but they know what they are doing by now.
A script is different, of course; removing that might actually affect
people.
jon
next prev parent reply other threads:[~2022-08-26 13:18 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
2022-08-26 2:19 ` Bagas Sanjaya
2022-08-26 2:24 ` Randy Dunlap
2022-08-26 13:18 ` Jonathan Corbet [this message]
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=87fshjw3cj.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--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).