From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Leo Li <leoyang.li@nxp.com>, Peter Rosin <peda@axentia.se>,
Richard Weinberger <richard@nod.at>,
Thierry Reding <thierry.reding@gmail.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: linux-next: trees being removed
Date: Tue, 20 Aug 2024 08:36:01 +1000 [thread overview]
Message-ID: <20240820083601.4eb41e96@canb.auug.org.au> (raw)
In-Reply-To: <20240813085147.786004fb@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Hi all,
On Tue, 13 Aug 2024 08:51:47 +1000 Stephen Rothwell <sfr@canb.auug.org.au> 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 kept (or
> later restored), just let me know (and update its branch).
>
> Tree Last commit date
> URL
> comits (if any)
> ---- ----------------
> djw-vfs 2023-08-04 08:20:57 -0700
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git#vfs-for-next
> drm-tegra 2023-04-06 14:02:33 +0200
> https://gitlab.freedesktop.org/drm/tegra.git#for-next
> pidfd 2023-07-02 11:14:54 -0700
> git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git#for-next
> soc-fsl 2023-06-08 17:56:26 -0500
> git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#next
> soc-fsl-fixes 2023-07-09 13:53:13 -0700
> git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#fix
> uml-fixes 2023-05-10 00:21:30 +0200
> git://git.kernel.org/pub/scm/linux/kernel/git/uml/linux.git#fixes
The above trees have now been removed from linux-next.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-08-19 22:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 22:51 linux-next: trees being removed 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 [this message]
-- 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-12-16 14:04 ` Thorsten Scherer
2025-12-18 23:40 ` Gabriel Krisman Bertazi
2025-12-18 23:57 ` Stephen Rothwell
2025-12-19 10:36 ` Miguel Ojeda
2025-12-19 10:41 ` Andreas Larsson
2025-12-19 11:53 ` Krzysztof Kozlowski
2025-12-19 12:01 ` Krzysztof Kozlowski
2025-12-20 0:36 ` Dennis Zhou
2026-01-05 21:51 ` Dipen Patel
2026-01-05 22:08 ` Stephen Rothwell
2026-02-09 12:33 ` Jean Delvare
2026-02-10 5:19 ` Stephen Rothwell
2026-02-10 12:25 ` Mark Brown
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-03-26 23:13 Stephen Rothwell
2024-03-27 4:16 ` Eric Biggers
2024-03-27 10:04 ` Alexandre Belloni
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
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=20240820083601.4eb41e96@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peda@axentia.se \
--cc=richard@nod.at \
--cc=thierry.reding@gmail.com \
--cc=vigneshr@ti.com \
/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