From: David Runge <dave@sleepmap.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39
Date: Tue, 21 Jul 2026 11:10:02 +0200 [thread overview]
Message-ID: <al83asltX9snvqq1@hmbx> (raw)
In-Reply-To: <20260720125805.wN3NFiBj@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On 2026-07-20 14:58:05 (+0200), Sebastian Andrzej Siewior wrote:
> It is there
> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/log/?h=linux-6.18.y-rt
> https://www.kernel.org/pub/linux/kernel/projects/rt/6.18/patches-6.18.37-rt6.tar.xz
>
> the problem is probably that it is not in the stable tree…
Hi Sebastian,
thanks for pointing me to the custom source tarballs and the relevant data in
the linux-rt-devel repository.
To understand this better: Is the 6.18 release series (and future release series
from then on) going to be developed in the linux-rt-devel repository, not the
linux-stable-rt repository?
As downstream package maintainer I am currently relying on the relevant git tags
to be available.
The linux-rt-devel repository seems to cover all new versions, but
linux-stable-rt appears to lack behind the upstream advertised LTS release
series.
In general, I would very much welcome a single repository, instead of the
current situation with two repositories, in case that is feasible for you.
Is there policy around when a specific release series is used in which
repository?
Best,
David
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-21 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 8:14 Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39 David Runge
2026-07-20 12:58 ` Sebastian Andrzej Siewior
2026-07-21 9:10 ` David Runge [this message]
2026-07-21 10:47 ` Sebastian Andrzej Siewior
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=al83asltX9snvqq1@hmbx \
--to=dave@sleepmap.de \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@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.