From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] centralize multistrap configuration generation
Date: Fri, 16 Feb 2018 12:35:28 +0100 [thread overview]
Message-ID: <edd1df30-4b60-6540-2ecc-4f3da324018a@siemens.com> (raw)
In-Reply-To: <61236588-c62b-b2f3-b5da-39ebd16fb371@ilbers.de>
Folks,
let's not discuss the legacy multistrap topic any further and focus on a
clean re-implementation via debootstrap. That will remove all needs to
translate into or from intermediate configuration files.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-02-16 11:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:15 [PATCH 0/2] Consolidate " claudius.heine.ext
2018-02-14 13:15 ` [PATCH 1/2] meta/classes/base: extend sys.path with lib directory claudius.heine.ext
2018-02-15 7:28 ` Jan Kiszka
2018-02-14 13:15 ` [PATCH 2/2] centralize multistrap configuration generation claudius.heine.ext
2018-02-15 7:28 ` Jan Kiszka
2018-02-15 8:16 ` Claudius Heine
2018-02-15 8:50 ` Jan Kiszka
2018-02-15 9:34 ` Alexander Smirnov
2018-02-15 10:05 ` Claudius Heine
2018-02-15 10:15 ` Jan Kiszka
2018-02-15 10:29 ` Alexander Smirnov
2018-02-15 11:27 ` Baurzhan Ismagulov
2018-02-15 13:17 ` Claudius Heine
2018-02-15 13:18 ` Jan Kiszka
2018-02-15 11:42 ` Baurzhan Ismagulov
2018-02-15 12:08 ` Claudius Heine
2018-02-15 12:37 ` Alexander Smirnov
2018-02-15 13:20 ` Claudius Heine
2018-02-15 13:39 ` Alexander Smirnov
2018-02-16 9:31 ` Claudius Heine
2018-02-16 10:35 ` Alexander Smirnov
2018-02-16 11:35 ` Jan Kiszka [this message]
2018-02-15 13:53 ` 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=edd1df30-4b60-6540-2ecc-4f3da324018a@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