From: Tom Zanussi <zanussi@kernel.org>
To: Pavel Machek <pavel@denx.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Wagner <wagi@monom.org>,
Clark Williams <williams@redhat.com>
Subject: Re: [ANNOUNCE] 4.19.132-rt59
Date: Tue, 14 Jul 2020 14:31:41 -0500 [thread overview]
Message-ID: <a9444792fd48b67493902b50a66a287fda0fb2c6.camel@kernel.org> (raw)
In-Reply-To: <20200714183512.GA18816@duo.ucw.cz>
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
next prev parent reply other threads:[~2020-07-14 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 16:58 [ANNOUNCE] 4.19.132-rt59 Tom Zanussi
2020-07-14 18:35 ` Pavel Machek
2020-07-14 19:31 ` Tom Zanussi [this message]
2020-07-14 19:43 ` Steven Rostedt
2020-07-14 19:48 ` Tom Zanussi
2020-07-15 6:29 ` Daniel Wagner
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=a9444792fd48b67493902b50a66a287fda0fb2c6.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=williams@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).