[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ad2962e-ff1f-4fe6-76e9-21c3936578a9@linux-m68k.org>
Date: Sat, 6 May 2023 10:17:44 +1000 (AEST)
From: Finn Thain <fthain@...ux-m68k.org>
To: Jonathan Corbet <corbet@....net>
cc: Bagas Sanjaya <bagasdotme@...il.com>,
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>,
Oliver Neukum <oliver@...kum.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 Fri, 5 May 2023, Jonathan Corbet wrote:
>
> Most of the 2.4 code has indeed been deleted *from current kernels*.
Is it okay to delete old code from -stable kernels?
> It's not clear to me why 2.4 documentation should be immune to that same
> process.
My message argued for removing 2.5 documentation and retaining the link
that gives credit to prior contributions.
> If we keep every 20-year-old reference, our docs will be even cruftier
> and less useful than they are now.
>
Since you're obviously being facetious, it's tempting to respond that
"churn is good because it reduces the average age of the code". But that
kind of exchange gets us nowhere.
I'd be curious to see an age histogram of the commentary in the source
code in the mainline kernel repository (or any other long-lived project).
I wonder if that has ever been measured.
Powered by blists - more mailing lists