From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: stable: queue/* branches no longer updated
Date: Wed, 30 Jul 2025 00:44:36 -0400 [thread overview]
Message-ID: <aImjNPvGPMqFu3RD@lappy> (raw)
In-Reply-To: <e6ea1805-3e82-476c-86a8-096b80bde74a@kernel.org>
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!
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-07-30 4:44 UTC|newest]
Thread overview: 5+ 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 [this message]
2025-07-30 8:38 ` Matthieu Baerts
2025-09-19 21:30 ` Matthieu Baerts
2026-02-11 10:10 ` 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=aImjNPvGPMqFu3RD@lappy \
--to=sashal@kernel.org \
--cc=matttbe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.