From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 55A583009E6; Tue, 14 Oct 2025 15:15:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760454908; cv=none; b=Tx6paOpDbOB+Gt7n2ZVqmaFOoNNXRm5xgw9mNvzv29+2+K6s0nCP3kINBB4EqGAfxkL0de741HJ9Bo1QMdrm2rFBvAnqxaJ4dzBPu+HwnvhGAiKzSZwzSSXxl4KvjMFELF9Mt0x6T3Xh9SJJ7k+q1fwS/9pkzIN29CqqiML/qQs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760454908; c=relaxed/simple; bh=m0i1QUBh4zJhtP8fKiyIIyRlwPYD2o/aXoX6SdDe2oI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=n1ifeS2EfgZx9W+ugT95+SN4wldrRALmqhPiz21GKcW7t5tx1SuvMyAgwF4bB7SsjpyxJqTSGHZq52Nm9XzKJUPJB+nOxrGYjaeeUDvNZmO0grJbTuLULyq/l1drT0tKw9Ps0xQqGtubUf2Jsw0CqHcgrznAeRRcrJwa6oI+SzE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=fAHzSTqz; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="fAHzSTqz" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net CD5D840B1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1760454903; bh=m0i1QUBh4zJhtP8fKiyIIyRlwPYD2o/aXoX6SdDe2oI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=fAHzSTqzngYXdnjB5R3lpag4tKXHXZME8EcB/Up/vM7PoU5MrU9jwB0qsiRpA9vve 50F9/438qkvYdb3VFif0VQuBWYGYVxrNy14bmG09Z1usYZCZQBkVCzK3STWVTW1F/r ng2Lm+RzLAaRZjrsh3yXEN3OHvMizzT2ObbHwQWqNaAJ/A3elj+GMdaEydMFPGyFZ/ jeMtMOeEr06wPMveKF3csaIPKGwxMVOhmEWYyypV3vSVZHIZDXc0GLEjrOp4VT6KD+ tQMxcPAgm9uMGZRJ5U9xEKMbiPnyst1HjqfWkjKjdrDYEa9w8Hfsel8t2tuoAef3Lv cMAE2rk+8g+Qw== Received: from localhost (unknown [IPv6:2601:280:4600:2da9::1fe]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id CD5D840B1E; Tue, 14 Oct 2025 15:15:02 +0000 (UTC) From: Jonathan Corbet To: Bagas Sanjaya , Linux Kernel Mailing List , Linux Documentation , Linux Kernel Workflows Cc: Dante Strock , Randy Dunlap , Bagas Sanjaya Subject: Re: [PATCH v2] Documentation: process: Arbitrarily bump kernel major version number In-Reply-To: <20250922074219.26241-1-bagasdotme@gmail.com> References: <20250922074219.26241-1-bagasdotme@gmail.com> Date: Tue, 14 Oct 2025 09:15:01 -0600 Message-ID: <87bjm9bjm2.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: workflows@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Bagas Sanjaya writes: > The big picture section of 2.Process.rst currently hardcodes major > version number to 5 since fb0e0ffe7fc8e0 ("Documentation: bring process > docs up to date"). As it can get outdated when it is actually > incremented (the recent is 6 and will be 7 in the near future), > arbitrarily bump it to 9, giving a headroom for a decade. > > Note that the version number examples are kept to illustrate the > numbering scheme. > > Signed-off-by: Bagas Sanjaya I made a minor tweak to make it clear that 9.x is an example; applied, thanks. jon