From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Bezdeka, Florian (T CED OES-DE)" <florian.bezdeka@siemens.com>,
"rpm@xenomai.org" <rpm@xenomai.org>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>,
"Kowalsky, Clara (T CED OES-DE)" <clara.kowalsky@siemens.com>
Subject: Re: linux-dovetail: Branch v6.6-dovetail1 was removed
Date: Fri, 2 Feb 2024 06:35:10 +0100 [thread overview]
Message-ID: <ddfb238b-30ed-4487-8615-091f5c27f2cf@siemens.com> (raw)
In-Reply-To: <84f36ac3a6e146a3301edc1503f257742af0c7ab.camel@siemens.com>
On 01.02.24 23:36, Bezdeka, Florian (T CED OES-DE) wrote:
> As this was merged to master now we seem to have a regression...
>
> [Resend with list in CC]
>
> On Wed, 2024-01-24 at 14:22 +0100, Florian Bezdeka wrote:
>> Hi all,
>>
>> this patch [1] in xenomai images - which I cannot find on the list -
>> references a branch named "v6.6-dovetail1" which does not exist.
>>
This is not supposed to be a branch but a tag. I had to create it while
starting the v6.6.y-dovetail branch. Fixed now in that repo.
That said, it would be good to refresh v6.6.y soon. Upstream is at
v6.6.15, we are at v6.6.
Jan
>> According to the project history on source.denx.de this branch never
>> existed, so I assume that kas cmdlines using opt-linux-6.6.yml were
>> never working.
>>
>> That brings me to the following question: How to fix that? For 6.6
>> there is no non -rebase branch available yet. Why is that? No plans to
>> maintain 6.6 as merge branch as we did for 5.10 and newer?
>>
>> [1] https://source.denx.de/Xenomai/xenomai-images/-/commit/3305ab5b3593b01dc08c59e170ac98be1f83f634
>>
>> Best regards,
>> Florian
>
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2024-02-02 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ae4513b93b5d14b59940daa604b9caef74fda40.camel@siemens.com>
2024-02-01 22:36 ` linux-dovetail: Branch v6.6-dovetail1 was removed Bezdeka, Florian
2024-02-02 5:35 ` Jan Kiszka [this message]
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=ddfb238b-30ed-4487-8615-091f5c27f2cf@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=clara.kowalsky@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=rpm@xenomai.org \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).