From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Baurzhan Ismagulov <ibr@ilbers.de>,
"Dalamagkidis,
Konstantinos" <konstantinos.dalamagkidis@siemens.com>,
Quirin Gylstorff <quirin.gylstorff@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Subject: Integration branch for pending patches
Date: Sun, 22 Sep 2019 20:21:12 +0200 [thread overview]
Message-ID: <706182d3-eda9-2bbc-f8d0-722c787efddb@siemens.com> (raw)
Hi all,
as we sometimes have delays in getting fixes and feature enhancements into
upstream, I've started a basic early integration branch. This shall help testing
patches quicker in combination with others. And that actually already paid off,
revealing an issue in one of the patches [1].
You can get the branch from
https://github.com/siemens.git jan/next
(https://github.com/siemens/isar/commits/jan/next)
It should contain all pending patches except for the following ones:
- meta/classes: generate bill of material from image (due to [1])
- CI: make gitlab-ci build verbose instead of quiet (due to [2])
- Add support for supplying more types of debian package relationships
(we really need to decide now if we want these additional recipe
APIs, and we need to document debianize as a whole)
If I missed anything, please let me know. The queue passed fast CI here and also
a build test with jailhouse-images.
Hopefully, this can help to speed up stabilization and merge of new patches a
bit. I will try to update this branch also in the future, as patches come in or
get merged.
Jan
[1]
https://groups.google.com/d/msgid/isar-users/c47f6e11-7f7f-22db-3dc2-1291f57a8a03%40siemens.com
[2]
https://groups.google.com/d/msgid/isar-users/32a6c1e3-5028-df8a-8127-ea1828082c29%40siemens.com
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
reply other threads:[~2019-09-22 18:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=706182d3-eda9-2bbc-f8d0-722c787efddb@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=konstantinos.dalamagkidis@siemens.com \
--cc=quirin.gylstorff@siemens.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