public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Pavel Machek <pavel@denx.de>,
	cip-dev@lists.cip-project.org, Chris.Paterson2@renesas.com,
	nobuhiro1.iwamatsu@toshiba.co.jp
Subject: Re: [ANNOUNCE] v6.1.102-cip26
Date: Tue, 13 Aug 2024 17:30:03 +0200	[thread overview]
Message-ID: <Zrt7+75ZR2DxGpi4@duo.ucw.cz> (raw)
In-Reply-To: <9fe32cd5-7159-4e53-b8e1-3db1f29fe383@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

Hi!

> > New -cip release 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-6.1.y-cip
> > https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-6.1.y-cip-rebase
> > 
> > And their content should be identical.
> > 
> > There are also tar archives, at:
> > 
> > https://mirrors.edge.kernel.org/pub/linux/kernel/projects/cip/
> 
> Did you push the tarball of this as well? I find 6.1.101-cip26-rt14 but
> only 6.1.101-cip25.

Let me retry. I got some weird problems with tags while pushing (it
seemed like linux-6.1.y-cip is not only head but also some other
object type).

Hopefully it works. If not, at least I should get some kind of error
message in my inbox.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-08-13 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 16:36 [ANNOUNCE] v6.1.102-cip26 Pavel Machek
2024-08-12 11:25 ` Jan Kiszka
2024-08-13 15:30   ` Pavel Machek [this message]
2024-08-13 15:47     ` Pavel Machek
2024-08-13 15:44   ` Pavel Machek
2024-08-14  4:43     ` Jan Kiszka
2024-08-14 10:30       ` 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=Zrt7+75ZR2DxGpi4@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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