Re: Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39

--QubuJ83SEyMb2IxQ
Content-Type: text/plain; protected-headers=v1; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Date: Tue, 21 Jul 2026 11:10:02 +0200
From: David Runge <[email protected]>
To: Sebastian Andrzej Siewior <[email protected]>
Cc: [email protected]
Subject: Re: Issues building RT patchset v6.18.13-rt4-rebase on top of
 v6.18.39

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=3Dlinux-6.18.y-rt
>    https://www.kernel.org/pub/linux/kernel/projects/rt/6.18/patches-6.18.=
37-rt6.tar.xz
>=20
> the problem is probably that it is not in the stable tree=E2=80=A6

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 s=
eries
=66rom 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

--QubuJ83SEyMb2IxQ
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQR8efy7g3Ll3lsX4JqQ1LlkHgkpcQUCal83agAKCRCQ1LlkHgkp
ca+4AQCPkHVxJnwRPth+QJ0SSfuV+PTSkHSQdxv+/J7MJPOdRQD8CBlFPCl6aK9d
H73SF5+PZsFtCPN3KZ4cQK/z/F5LygI=
=YWlb
-----END PGP SIGNATURE-----

--QubuJ83SEyMb2IxQ--