Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp1610114rwr; Fri, 5 May 2023 17:37:51 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ74+xWnb+WQPqcr+c694+rOhX1J9Q/PaMyNf0mN3ax+zLbZVFFRsIPWj7r3aTSI5EqdPEWb X-Received: by 2002:a17:90a:e56:b0:246:97d2:dc27 with SMTP id p22-20020a17090a0e5600b0024697d2dc27mr3372490pja.42.1683333470622; Fri, 05 May 2023 17:37:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683333470; cv=none; d=google.com; s=arc-20160816; b=DM345dvHD0EBRjC0lBiahJbrm5s2mSLpZu8b6MXYa2dWZfwKOhU0kjBFp4sjl4VwNp oTc6bHxIQwwkvuyckL1NIJdCMyCS9k/yASZ09i13LHf4W8dIXz7/CBUgcAY6jaGSTTis bN9a9k+h0My2J9EOTZ2mhfUEtTV/l7Z9xDDUhXt+x1qz8lnrjhw/gPZwAm6n2fz2Fvk8 gDbSQh9qsQbVrWVpvpqZkBNJikYghfxAH+o6nsPURXnf8GufoP/5p9iMi2fWnzeggmYU 4vjVjEEXoY4s/I+HPF36TE2aaPPMYKdLyRVWMZAGhE98fTRMdgdH2T5Z80ugoXsy904w 4JMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:feedback-id:dkim-signature; bh=gDkdPLFGHEgwBa8neDNDtTbJzRE+q/3RtYLzD+Pf+P8=; b=y8KqzjcgmpFHGOux3Kxsz+xgMZTwxdpanZPbc/rT3UiIG7P/QKmXtgqPVZJSm9J5Ns qHmIjkNk8m0TcY2+80Gr8YFzT5iNUM7xR56iebPumCBinHDxQRX97LiveLBDn/wgV6Le +RfGyiA8haSC3jIbilwdQQFu4oBmStxpFRqBsToZEK/S3V5EddXoz1ETaNw9p/KldXEJ Eou5seydgJ+kOxwJKDXLZW8SR5B7R/49/15fJxSiYL0XFW7U4QIlOTcV2LItTiBJnHvA AVB58p+s2pn2uUIzuQFHJJXJyEheLL7yjhedzV+odXOW+aVkgBZ/2oLR+AsvDeIf3IUR i+AA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=Q8XG2AWQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cp18-20020a17090afb9200b002476be78cd2si7479352pjb.121.2023.05.05.17.37.35; Fri, 05 May 2023 17:37:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=Q8XG2AWQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231441AbjEFAOB (ORCPT + 99 others); Fri, 5 May 2023 20:14:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55958 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229990AbjEFANv (ORCPT ); Fri, 5 May 2023 20:13:51 -0400 Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A58E56E86; Fri, 5 May 2023 17:13:50 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 6E1B232009C0; Fri, 5 May 2023 20:13:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 05 May 2023 20:13:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1683332029; x=1683418429; bh=gDkdPLFGHEgwB a8neDNDtTbJzRE+q/3RtYLzD+Pf+P8=; b=Q8XG2AWQgyCMi09ZyMm+KsQ0hhprv mpooklDQKeung+QWuBSAj/oCp/IpivM2K7XnXh3Qvn8lhOiJOYAxClS/rU1xwfwl 9dGWxnIg16hEvLdtmI/FetfUGGPZpda4XCQrrmaOZPxJfuDg9NuFQq3OY3pYceFb nSdkV0WKCNuVg1u7V5B8bZok6hBXsOVjmSxeze5cGpq0tN+o78IZzjqnxwqf04uy 8EBcx3yLS09+94+6vwFIdokFBhtS+BY3E4hh2mxo7dOWvNWUOpIkEyXYg4VeQ46X auuC21N7RCmqsHgckHBJyd0kMyFOJaOhquTZCyFSFOXRUdQR9l9YL9Sjw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeeffedgfedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevufgjkfhfgggtsehttdertddttddvnecuhfhrohhmpefhihhnnhcu vfhhrghinhcuoehfthhhrghinheslhhinhhugidqmheikehkrdhorhhgqeenucggtffrrg htthgvrhhnpeelueehleehkefgueevtdevteejkefhffekfeffffdtgfejveekgeefvdeu heeuleenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hfthhhrghinheslhhinhhugidqmheikehkrdhorhhg X-ME-Proxy: Feedback-ID: i58a146ae:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 5 May 2023 20:13:45 -0400 (EDT) Date: Sat, 6 May 2023 10:17:44 +1000 (AEST) From: Finn Thain To: Jonathan Corbet cc: Bagas Sanjaya , Linux SCSI , Linux Documentation , Linux Kernel Mailing List , Linux Kernel Janitors , Oliver Neukum , Ali Akcaagac , Jamie Lenehan , "James E.J. Bottomley" , "Martin K. Petersen" Subject: Re: [PATCH 3/3] Documentation: scsi: dc395x: Remove reference to 2.4 driver In-Reply-To: <87pm7enbpo.fsf@meer.lwn.net> Message-ID: <3ad2962e-ff1f-4fe6-76e9-21c3936578a9@linux-m68k.org> References: <20230505082704.16228-1-bagasdotme@gmail.com> <20230505082704.16228-4-bagasdotme@gmail.com> <87pm7enbpo.fsf@meer.lwn.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_NONE, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.