public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Adler, Michael" <michael.adler@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
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 07:55:27 +0000	[thread overview]
Message-ID: <20190329075525.g6qnnzwvgl2hplhd@demogorgon> (raw)
In-Reply-To: <16bf1e92-4b7d-e712-4709-f16fe02f0bf7@ilbers.de>

> 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 ;)

Kind regards,
  Michael

-- 
Michael Adler
Siemens AG, Corporate Technology, CT RDA IOT SES-DE, Otto-Hahn-Ring 6, 81739 Munich, Germany

Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Joe Kaeser, Chairman, President and Chief Executive Officer; Roland Busch, Lisa Davis, Klaus Helmrich, Janina Kugel, Siegfried Russwurm, Ralf P. Thomas; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322

  parent reply	other threads:[~2019-03-29  7:55 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 [this message]
2019-03-29  8:45                 ` Maxim Yu. Osipov
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=20190329075525.g6qnnzwvgl2hplhd@demogorgon \
    --to=michael.adler@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mosipov@ilbers.de \
    /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