From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Richard Weinberger <richard@nod.at>,
Theodore Ts'o <tytso@mit.edu>, Tyler Hicks <code@tyhicks.com>
Subject: Re: linux-next: trees being removed
Date: Wed, 27 Mar 2024 11:04:21 +0100 [thread overview]
Message-ID: <20240327100421604167cd@mail.local> (raw)
In-Reply-To: <20240327041653.GA35281@sol.localdomain>
On 26/03/2024 21:16:53-0700, Eric Biggers wrote:
> On Wed, Mar 27, 2024 at 10:13:09AM +1100, Stephen Rothwell wrote:
> > The following trees are going to be removed from linux-next because they
> > have not been updated in more than a year. If you want a tree restored,
> > just let me know (and update its branch).
> >
> > Tree Last commit date
> > URL
> > comits (if any)
> > ---- ----------------
> > ecryptfs 2023-03-24 17:26:44 -0500
> > git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git#next
> > c1cc2db21607 ("ecryptfs: keystore: Fix typo 'the the' in comment")
> > a3d78fe3e1ae ("fs: ecryptfs: comment typo fix")
> > fscrypt-current 2023-03-18 21:08:03 -0700
> > git://git.kernel.org/pub/scm/fs/fscrypt/linux.git#for-current
> > fsverity-current 2023-03-15 22:50:41 -0700
> > git://git.kernel.org/pub/scm/fs/fsverity/linux.git#for-current
> > modules-fixes 2023-02-06 08:45:55 -0800
> > git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-linus
> > rtc-fixes 2023-01-23 23:33:47 +0100
> > git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git#rtc-fixes
> > tee-fixes 2023-02-12 14:10:17 -0800
> > https://git.linaro.org/people/jens.wiklander/linux-tee.git#fixes
> > ubifs-fixes 2023-01-21 16:27:01 -0800
> > git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git#fixes
>
> fscrypt-current and fsverity-current are technically still in use. I just
> haven't used them recently because there haven't been any bug fixes that needed
> to go in while other commits were already applied for the next merge window.
>
> I've updated them to v6.9-rc1.
>
> I'd guess that some of those *-fixes branches have something similar going on,
> where they may be rarely used fixes branches as opposed to the main development
> branch.
>
This is exactly my case. I don't mind my branch being dropped and I can
ask to add it back once I have urgent fixes.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-03-27 10:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 23:13 linux-next: trees being removed Stephen Rothwell
2024-03-27 4:16 ` Eric Biggers
2024-03-27 10:04 ` Alexandre Belloni [this message]
2024-03-27 11:18 ` Stephen Rothwell
2024-03-27 12:46 ` Alexandre Belloni
2024-03-27 21:33 ` Richard Weinberger
2024-04-01 21:13 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-12-15 7:41 Stephen Rothwell
2025-12-15 14:55 ` Chuck Lever
2025-12-15 21:21 ` Stephen Rothwell
2025-12-15 15:43 ` Lee Jones
2025-12-15 18:09 ` Uwe Kleine-König
2025-12-16 5:19 ` Stephen Rothwell
2025-02-11 22:56 Stephen Rothwell
2025-02-12 16:32 ` Vineet Gupta
2025-02-16 11:11 ` Stephen Rothwell
2025-02-19 19:58 ` Vineet Gupta
2025-02-19 21:52 ` Stephen Rothwell
2025-02-16 11:42 ` Stephen Rothwell
2025-03-05 21:34 ` Nick Terrell
2025-03-05 21:47 ` Stephen Rothwell
2024-08-12 22:51 Stephen Rothwell
2024-08-13 5:13 ` Peter Rosin
2024-08-13 6:59 ` Stephen Rothwell
2024-08-14 10:06 ` Vignesh Raghavendra
2024-08-14 10:55 ` Stephen Rothwell
2024-08-19 22:36 ` Stephen Rothwell
2024-01-24 2:01 Stephen Rothwell
2024-01-24 2:10 ` Jason A. Donenfeld
2024-01-24 2:32 ` Stephen Rothwell
2024-01-24 15:41 ` Mike Marshall
2024-01-24 21:49 ` Stephen Rothwell
2024-01-24 15:50 ` Lee Jones
2024-01-24 21:56 ` Stephen Rothwell
2024-02-06 10:50 ` Jean Delvare
2024-02-06 22:13 ` Stephen Rothwell
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=20240327100421604167cd@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=code@tyhicks.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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).