From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
"Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users@googlegroups.com
Subject: Re: [PATCH v4 07/14] Move debian distro conf files to meta
Date: Wed, 23 Jan 2019 06:56:55 +0100 [thread overview]
Message-ID: <c81d173f-7a94-c34e-e05c-57a4fc0a881e@siemens.com> (raw)
In-Reply-To: <d8f97830-a3e4-49ce-2541-bc252f997e42@siemens.com>
On 21.01.19 10:57, [ext] Claudius Heine wrote:
> Hi Jan,
>
> On 17/01/2019 17.36, Maxim Yu. Osipov wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> This only keeps specialties and examples in meta-isar, allowing to base
>> normal Debian layers solely on meta.
>
> Maybe I am a bit late commenting here. But I think I remember suggesting this
> layout or some form of it at some point in the past:
>
> - meta-isar
> Base functionality
> - meta-isar-debian
> Debian configuration
> - meta-isar-example
> Example/Test-case stuff
I'm open for different namings, and I'm also open for a split-up of the core
layer - provided someone delivers a good use case. Currently, I don't see that
use case, nor its implementation, thus this folding of what you call meta-isar
and meta-isar-debian. The first step was to separate example recipes and
configs, and that is achieved now.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2019-01-23 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 16:36 Maxim Yu. Osipov
2019-01-18 15:27 ` Jan Kiszka
2019-01-18 15:43 ` Maxim Yu. Osipov
2019-01-18 15:59 ` Jan Kiszka
2019-01-21 9:57 ` Claudius Heine
2019-01-23 5:56 ` Jan Kiszka [this message]
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=c81d173f-7a94-c34e-e05c-57a4fc0a881e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.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