From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jean Delvare <jdelvare@suse•de>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
David Miller <davem@davemloft•net>,
"Eric W. Biederman" <ebiederm@xmission•com>,
Florian Fainelli <f.fainelli@gmail•com>,
Hector Martin <marcan@marcan•st>,
"Jason A. Donenfeld" <Jason@zx2c4•com>,
Lee Jones <lee@kernel•org>, Micah Morton <mortonm@chromium•org>,
Mike Marshall <hubcap@omnibond•com>, Pavel Machek <pavel@ucw•cz>,
Theodore Ts'o <tytso@mit•edu>
Subject: Re: linux-next: trees being removed
Date: Wed, 7 Feb 2024 09:13:53 +1100 [thread overview]
Message-ID: <20240207091353.2d16ac11@canb.auug.org.au> (raw)
In-Reply-To: <d5e68f29d6c835848295c10bac964da7a57f1bfe.camel@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
Hi Jean,
On Tue, 06 Feb 2024 11:50:44 +0100 Jean Delvare <jdelvare@suse•de> wrote:
>
> On Wed, 2024-01-24 at 13:01 +1100, Stephen Rothwell wrote:
> >
> > Tree Last commit date
> > URL
> > commits (if any)
> > -----------------------------------------
> > (...)
> > dmi 2022-09-23 14:53:14 +0200
> > git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git#dmi-for-next
>
> This is still where I would put updates to the DMI subsystem, but it
> turns out there haven't been any for some time now, and I'm not aware
> of any pending issue.
I am happy to restore it if you want.
> Out of curiosity, why do inactive branches bother you?
It is mostly just a way to get rid of abandoned trees. Also, one of
the checks I do requires me to reference all the commits between the
merge base of each tree and Linus' tree. If the base (and top commit)
of a tree has not been updated for a year, that means checking 40,000+
commits which takes a noticeable amount of time. Also just merging
such a tree has a noticeable delay. An empty tree (relative to Linus'
tree) doesn't cost much, of course.
> I can certainly update that branch if it makes your life easier.
Yeah, even just resetting it to Linus' tree at each -rc1 will help.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-06 22:14 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 2:01 linux-next: trees being removed 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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-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
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
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
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=20240207091353.2d16ac11@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Jason@zx2c4$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ebiederm@xmission$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=hubcap@omnibond$(echo .)com \
--cc=jdelvare@suse$(echo .)de \
--cc=lee@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marcan@marcan$(echo .)st \
--cc=mortonm@chromium$(echo .)org \
--cc=pavel@ucw$(echo .)cz \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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