From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: "Adler, Michael" <michael.adler@siemens.com>
Cc: "henning.schild@siemens.com" <henning.schild@siemens.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods
Date: Fri, 29 Mar 2019 09:45:13 +0100 [thread overview]
Message-ID: <ee98ea03-8dd3-437c-2872-c59d6af4cd63@ilbers.de> (raw)
In-Reply-To: <20190329075525.g6qnnzwvgl2hplhd@demogorgon>
Hi Michael,
On 3/29/19 8:55 AM, Adler, Michael wrote:
>> With the removal of jessie support I may proceed with the integration of
>> this patch.
>
> Yes, please go ahead! Getting rid of the loopback device makes the CI setup for ISAR **a lot** easier because all you need then are privileged containers.
> In fact, I'm currently using a fork of ISAR with this patch applied and I have a fully working ISAR CI build on AWS EC2. More details to follow soon ;)
I've applied the patch in the 'next' branch.
In one week 'master' will be synced with the 'next'.
Thanks,
Maxim.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2019-03-29 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 13:04 [PATCH 0/1] Refactor ext4 image class claudius.heine.ext
2019-02-18 13:04 ` [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods claudius.heine.ext
2019-02-19 9:25 ` Henning Schild
2019-02-26 11:35 ` cedric_hombourger
2019-02-26 11:56 ` Jan Kiszka
2019-02-26 12:12 ` Henning Schild
2019-02-26 12:24 ` Hombourger, Cedric
2019-03-28 9:58 ` Maxim Yu. Osipov
2019-03-28 12:02 ` Hombourger, Cedric
2019-03-29 7:55 ` Adler, Michael
2019-03-29 8:45 ` Maxim Yu. Osipov [this message]
2019-02-27 9:28 ` [PATCH 0/1] Refactor ext4 image class Maxim Yu. Osipov
2019-03-28 12:40 ` Maxim Yu. Osipov
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=ee98ea03-8dd3-437c-2872-c59d6af4cd63@ilbers.de \
--to=mosipov@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=michael.adler@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