lkml.org 
[lkml]   [2020]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [ANNOUNCE] 4.19.132-rt59
From
Date
Hi Pavel,

On Tue, 2020-07-14 at 20:35 +0200, Pavel Machek wrote:
> Hi!
>
> >
> > I'm pleased to announce the 4.19.132-rt59 stable release.
> >
> > This release is just an update to the new stable 4.19.132
> > version and no RT specific changes have been made.
> >
> > You can get this release via the git tree at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-
> > rt.git
> >
> > branch: v4.19-rt
> > Head SHA1: 1eebf4069aa37e54330cce9a42608517ea6996fe
> >
> > Or to build 4.19.132-rt59 directly, the following patches should be
> > applied:
>
> Thanks a lot.
>
> But now I am confused, I completely missed announcements for
> v4.19.127-rt55 to v4.19.131-rt58.
>
> And for example -rt56 is not listed in
>
>
https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/4.19/older/sha256sums.asc
>

Right, this is because we up the rt version every time we merge a
stable version and have conflicts, and in this release there were a
lot, so it jumped from -rt55 to -rt59. We only announce the releases
and not the intervening version bumps, which is why you couldn't find
any announcements for them.

There are more details about exactly how the version numbers change
here:

https://wiki.linuxfoundation.org/realtime/documentation/start

> ...aha, and the versions do not have signed tags, either:
>
> pavel@amd:~/cip/k$ git show v4.19.131-rt58
> fatal: ambiguous argument 'v4.19.131-rt58': unknown revision or path
> not in the working tree.
>

Yeah, thanks for pointing that out. Looks like my script doesn't push
the intervening tags correctly, but I've pushed them out now.

> Is that because they were created just as quick steps towards -rt59?
>

Yeah, pretty much.

Thanks,

Tom

> Best regards,
> Pavel

\
 
 \ /
  Last update: 2020-07-14 21:33    [W:0.059 / U:0.800 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site