linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst
Date: Thu, 25 Aug 2022 14:53:35 +0700	[thread overview]
Message-ID: <76b2dbcf-70cf-aca8-4ccc-b2a73063b8db@gmail.com> (raw)
In-Reply-To: <CAKXUXMwLofvhBXqzdoq_q_89jZ8THU0WX=DY+RnCo=PN7QqspA@mail.gmail.com>

On 8/25/22 14:35, Lukas Bulwahn wrote:
> Randy, would you know if there are still users out there?
> Would it help to replace this script with a minimal script that only
> reports to "Please use git to obtain a recent repository. Update
> versions and apply patches with git in a controlled way.".
> 
> If someone complains, we revert the patch. If no one complains within
> a year or two, we could consider shutting down the infrastructure
> creating those patch archives as well, and delete the documentation
> referring to that.

As a refresher: besides Linus's tree (mainline), there is also stable
tree, which is maintained by Greg and Sasha. Most users uses the latter.
So, in case we add warning message to scripts/patch-kernel, we should say
"This script is deprecated; please clone stable tree at [1] with git
instead. If you'd like to apply patches, use git am. If you already have
the tree, use git fetch and git merge to update stable branch of your
choosing."

Thanks.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

-- 
An old man doll... just what I always wanted! - Clara

  parent reply	other threads:[~2022-08-25  7:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  8:08 [PATCH] docs: Update version number from 5.x to 6.x in README.rst Lukas Bulwahn
2022-08-25  3:08 ` Bagas Sanjaya
2022-08-25  7:27   ` Lukas Bulwahn
2022-08-25  3:24 ` Randy Dunlap
2022-08-25  7:35   ` Lukas Bulwahn
2022-08-25  7:39     ` Randy Dunlap
2022-08-25  7:53     ` Bagas Sanjaya [this message]
2022-08-25 18:48 ` Jonathan Corbet
2022-08-26  2:19   ` Bagas Sanjaya
2022-08-26  2:24     ` Randy Dunlap
2022-08-26 13:18     ` Jonathan Corbet
2022-08-26  8:28   ` Bagas Sanjaya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76b2dbcf-70cf-aca8-4ccc-b2a73063b8db@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rdunlap@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).