[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8536273d-20a4-1993-1381-b50e44701835@suse.com>
Date: Tue, 9 May 2023 10:55:46 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Jonathan Corbet <corbet@....net>,
Finn Thain <fthain@...ux-m68k.org>,
Bagas Sanjaya <bagasdotme@...il.com>
Cc: Linux SCSI <linux-scsi@...r.kernel.org>,
Linux Documentation <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kernel Janitors <kernel-janitors@...r.kernel.org>,
Ali Akcaagac <aliakc@....de>,
Jamie Lenehan <lenehan@...bble.org>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH 3/3] Documentation: scsi: dc395x: Remove reference to 2.4
driver
On 05.05.23 15:34, Jonathan Corbet wrote:
> Finn Thain <fthain@...ux-m68k.org> writes:
>
>> On Fri, 5 May 2023, Bagas Sanjaya wrote:
>> Would it make a difference if someone does run that? Were you planning to
>> delete the source code for the 2.4 kernel too?
>
> Most of the 2.4 code has indeed been deleted *from current kernels*.
> It's not clear to me why 2.4 documentation should be immune to that same
> process. If we keep every 20-year-old reference, our docs will be even
> cruftier and less useful than they are now.
Hi,
the documentation of a kernel should document that kernel.
Now, we have a perfectly fine tool named "git" which allows
for metadocumentation. May I suggest that you respin the patch
and include a link to the old stuff, which somebody has been
nice enough to find, in the change log?
Regards
Oliver
Powered by blists - more mailing lists