From: Matthieu Baerts <matttbe@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: stable: queue/* branches no longer updated
Date: Tue, 6 Oct 2026 11:45:39 +0200 [thread overview]
Message-ID: <905f6658-ac80-4d3e-b66b-d14ff0d4bf25@kernel.org> (raw)
In-Reply-To: <asS7KK444n7U01u0@laps>
On 06/10/2026 11:11, Sasha Levin wrote:
> On Mon, Oct 05, 2026 at 07:40:33PM +0200, Matthieu Baerts wrote:
>> Hi Sasha,
>>
>> On 05/08/2026 18:07, Sasha Levin wrote:
>>> On Wed, Aug 05, 2026 at 05:16:10PM +0200, Matthieu Baerts wrote:
>>>> Hi Sasha,
>>>>
>>>> On 11/02/2026 11:10, Matthieu Baerts wrote:
>>>>> Hi Sasha,
>>>>>
>>>>> On 19/09/2025 23:30, Matthieu Baerts wrote:
>>>>>> Hi Sasha,
>>>>>>
>>>>>> On 30/07/2025 06:44, Sasha Levin wrote:
>>>>>>> On Mon, Jul 28, 2025 at 11:06:17AM +0200, Matthieu Baerts wrote:
>>>>>>>> Hi Sasha,
>>>>>>>>
>>>>>>>> Thank you for maintaining the stable versions with Greg!
>>>>>>>>
>>>>>>>> If I remember well, you run some scripts on your side to
>>>>>>>> maintain the
>>>>>>>> queue/* branches in the linux-stable-rc Git tree [1], is that
>>>>>>>> correct?
>>>>>>>>
>>>>>>>> These branches have not been updated for a bit more than 3 weeks.
>>>>>>>> Is it
>>>>>>>> normal?
>>>>>>>>
>>>>>>>> Personally, I find them useful. But if it is just me, I can work
>>>>>>>> without
>>>>>>>> them.
>>>>>>>
>>>>>>> Nope, it's a bug!
>>>>>>>
>>>>>>> Looks like git was throwing:
>>>>>>>
>>>>>>> fatal: Unable to create '/home/sasha/data/stable-queue-builder/
>>>>>>> linux-
>>>>>>> stable/.git/index.lock': File exists.
>>>>>>>
>>>>>>> Another git process seems to be running in this repository, e.g.
>>>>>>> an editor opened by 'git commit'. Please make sure all processes
>>>>>>> are terminated then try again. If it still fails, a git process
>>>>>>> may have crashed in this repository earlier:
>>>>>>> remove the file manually to continue.
>>>>>>>
>>>>>>>
>>>>>>> Which my script was promptly ignoring...
>>>>>>>
>>>>>>> Fixed now, thanks for the heads up!
>>>>>>
>>>>>> It looks like these branches are no longer updated. Do you mind
>>>>>> checking
>>>>>> on your side please? :)
>>>>>
>>>>> These stable queue/* branches have not been updated for more than two
>>>>> weeks. Do you mind checking if there is something stuck on your side,
>>>>> please? :)
>>>> It looks like the last update was from 2 months ago. When you have a
>>>> chance, do you mind fixing your script please? (no urgency on my side)
>>>> Cheers,
>>>> Matt
>>>
>>> Sorry, should be fixed now
>> Sorry, do you mind checking again, please? :)
>>
>> (Maybe I shouldn't rely on them to send patches depending on others from
>> the queue.)
>
> One day I'll figure this out :) It should be back up.
:) It is, thank you!
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-10-06 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 9:06 stable: queue/* branches no longer updated Matthieu Baerts
2025-07-30 4:44 ` Sasha Levin
2025-07-30 8:38 ` Matthieu Baerts
2025-09-19 21:30 ` Matthieu Baerts
2026-02-11 10:10 ` Matthieu Baerts
2026-08-05 15:16 ` Matthieu Baerts
2026-08-05 16:07 ` Sasha Levin
2026-08-05 16:18 ` Matthieu Baerts
2026-10-05 17:40 ` Matthieu Baerts
2026-10-06 9:11 ` Sasha Levin
2026-10-06 9:45 ` Matthieu Baerts [this message]
2026-10-19 17:51 ` Matthieu Baerts
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=905f6658-ac80-4d3e-b66b-d14ff0d4bf25@kernel.org \
--to=matttbe@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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