From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 0/3] CI fixes and cleanups
Date: Thu, 1 Sep 2022 15:49:09 +0200 [thread overview]
Message-ID: <cover.1662040151.git.jan.kiszka@siemens.com> (raw)
See patches for details.
Jan
Jan Kiszka (3):
ci: Switch qemu-amd64-secure-boot-buster to 5.10 kernel
ci: Clean up redundant statements
ci: Rename empty extension case
.gitlab-ci.yml | 11 +++--------
scripts/deploy-cip-core.sh | 2 +-
2 files changed, 4 insertions(+), 9 deletions(-)
--
2.35.3
next reply other threads:[~2022-09-01 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:49 Jan Kiszka [this message]
2022-09-01 13:49 ` [isar-cip-core][PATCH 1/3] ci: Switch qemu-amd64-secure-boot-buster to 5.10 kernel Jan Kiszka
2022-09-01 13:49 ` [isar-cip-core][PATCH 2/3] ci: Clean up redundant statements Jan Kiszka
2022-09-01 13:49 ` [isar-cip-core][PATCH 3/3] ci: Rename empty extension case Jan Kiszka
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=cover.1662040151.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.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