From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 18F0EC43381 for ; Sun, 24 Feb 2019 12:54:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D97A720652 for ; Sun, 24 Feb 2019 12:54:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1551012893; bh=zUgthBSJZBzfTrB5LGn0lHCj5A75XcY3L2t95cXkzfs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=LeVi1ECHQxMA6G5K/cG/R1NM6sGiUsraumQwt24y3nGrkcfRmpDq4XR2/p7IPxNsS HEsS4gm4dgJW9xDXZCYsbdqvjsatDGhp79Xm5bazqxCOlQSn9BZHwWw2DBeTlbn//J kRS4ojigO4c2aS2Eor/jokFo0Y/3Q7Swoquz6F9w= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728282AbfBXMyw (ORCPT ); Sun, 24 Feb 2019 07:54:52 -0500 Received: from mail.kernel.org ([198.145.29.99]:50280 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725956AbfBXMyw (ORCPT ); Sun, 24 Feb 2019 07:54:52 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0826020652; Sun, 24 Feb 2019 12:54:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1551012891; bh=zUgthBSJZBzfTrB5LGn0lHCj5A75XcY3L2t95cXkzfs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=qwx/NwgLykiphngUImDzg352dttpRZ0Az0u7Z4lAUKsPALAxze5L1sj/6XzlNRugn /fGhiz44z6tn3D1fE/76hgYRSThlpWL8twmHsOLGBwBoPdmQwwVr8bvMT2fBtqjaAb 3mIB1rpVzkIikdIwmCRjYk5ZP3hhTNrHtaGolZSk= Date: Sun, 24 Feb 2019 13:54:49 +0100 From: Greg KH To: Federico Vaga Cc: Zenghui Yu , corbet@lwn.net, linux-doc@vger.kernel.org, LKML , Andrew Morton Subject: Re: [PATCH] Documentation/process/howto: Update for 4.x -> 5.x versioning Message-ID: <20190224125449.GC10876@kroah.com> References: <4160738.QP7Yp4kBzP@harkonnen> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4160738.QP7Yp4kBzP@harkonnen> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 24, 2019 at 11:16:56AM +0100, Federico Vaga wrote: > hello, > > I have just a general observation for the community, not related to the > content of this patch, but related with the idea behind. > > Is it really important to specify the major release number in the documents? . > Can't we just use a generic x.y.z, or a more generic statement? > > When you open a documentation page like > > https://www.kernel.org/doc/html/latest/ > > you will see the release number in the top left corner, which implies that > what you read is (should be) valid for that version. And if you read from the > sources you should know which version you checked out, and if you don't you > can always verify. > > I do not see the added value of having those numbers in the documents, unless > the purpose is to highlight some specific exceptions. > > Am I missing some important reasons that justify these numbers? Nothing really, it's just "history". Given that the "major" number only changes every 3-4 years, it's not all that big of a deal. If you can think of a way to write these documents such that they do not depend on a version number at all, I'm sure no one would object to those patches. thanks, greg k-h