From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Deploying KERNEL/INITRD_IMAGE vs. multiconfig
Date: Wed, 31 Jan 2018 10:46:00 +0100 [thread overview]
Message-ID: <7f15472d-f918-ec9a-0f47-4bb040053787@siemens.com> (raw)
Hi all,
as Henning correctly remarked yesterday while we were discussing the
deployment of vmlinuz-* and initrd-* to tmp/deploy/images: This is
broken /wrt multiconfig because it does not take name collisions into
account when building similar images in parallel.
But what is the role of this deployment in current Isar? Can we solve
the conflict somehow while maintaining that? Comments, ideas?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
reply other threads:[~2018-01-31 9:46 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=7f15472d-f918-ec9a-0f47-4bb040053787@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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