From: Pavel Machek <pavel@denx.de>
To: Tom Zanussi <zanussi@kernel.org>
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>,
Pavel Machek <pavel@denx.de>
Subject: Re: [ANNOUNCE] 4.19.132-rt59
Date: Tue, 14 Jul 2020 20:35:12 +0200 [thread overview]
Message-ID: <20200714183512.GA18816@duo.ucw.cz> (raw)
In-Reply-To: <82932b48972f38fccf9920e2ec75b555c2b2494a.camel@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
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
...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.
Is that because they were created just as quick steps towards -rt59?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-07-14 18:35 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 [this message]
2020-07-14 19:31 ` Tom Zanussi
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=20200714183512.GA18816@duo.ucw.cz \
--to=pavel@denx.de \
--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=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=williams@redhat.com \
--cc=zanussi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox