From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pavel Machek <pavel@nabladev.com>,
cip-dev@lists.cip-project.org, Chris.Paterson2@renesas.com
Subject: Re: [ANNOUNCE] v5.10.247-cip68-rt30
Date: Mon, 12 Jan 2026 14:59:01 +0100 [thread overview]
Message-ID: <b211ca2c-033f-427f-ac3c-9e9d2a16acf1@siemens.com> (raw)
In-Reply-To: <aWLVHnFYQWsNWmjj@duo.ucw.cz>
On 10.01.26 23:39, Pavel Machek wrote:
> Hi!
>
> New realtime trees should be available at kernel.org.
>
> Trees are available at
>
> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-5.10.y-cip-rt
> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-5.10.y-cip-rt-rebase
>
> And their content should be identical. There are also tar archives, at:
>
> https://mirrors.edge.kernel.org/pub/linux/kernel/projects/cip/
>
Could it be that you forgot to upload the tarball?
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2026-01-12 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 22:39 [ANNOUNCE] v5.10.247-cip68-rt30 Pavel Machek
2026-01-12 13:59 ` Jan Kiszka [this message]
2026-01-12 18:28 ` [cip-dev] " Pavel Machek
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=b211ca2c-033f-427f-ac3c-9e9d2a16acf1@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@nabladev.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