[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202403271246389692cfda@mail.local>
Date: Wed, 27 Mar 2024 13:46:38 +0100
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Eric Biggers <ebiggers@...nel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jaegeuk Kim <jaegeuk@...nel.org>,
Jens Wiklander <jens.wiklander@...aro.org>,
Luis Chamberlain <mcgrof@...nel.org>,
Richard Weinberger <richard@....at>, Theodore Ts'o <tytso@....edu>,
Tyler Hicks <code@...icks.com>
Subject: Re: linux-next: trees being removed
On 27/03/2024 22:18:19+1100, Stephen Rothwell wrote:
> Hi Alexandre,
>
> On Wed, 27 Mar 2024 11:04:21 +0100 Alexandre Belloni <alexandre.belloni@...tlin.com> wrote:
> >
> > 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.
>
> Or you could just update it to -rc1 every merge window or so and it
> will hang around. I don't mind keeping branches around that will get
> used sometime. I just don't like them being too old.
I've done that now and I'll try to remember to update at each -rc1.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Powered by blists - more mailing lists