public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 5/8] Add qemuarm64-stretch multiconfig
Date: Mon, 19 Feb 2018 13:36:20 +0100	[thread overview]
Message-ID: <131fdcc4-1030-c8b5-7404-b93ddbe8d2aa@siemens.com> (raw)
In-Reply-To: <11c0b40e-c34e-bcb6-0f98-c24999e2f3a1@ilbers.de>

On 2018-02-19 13:19, Alexander Smirnov wrote:
> On 02/19/2018 02:15 PM, Jan Kiszka wrote:
>> On 2018-02-19 11:23, Alexander Smirnov wrote:
>>> On 02/16/2018 11:52 AM, Jan Kiszka wrote:
>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>
>>>> Extend the image build script as needed and add a multiconfig that
>>>> allows to build a qemuarm64 target using stretch. Also add a machine
>>>> config for QEMU.
>>>
>>> This patch makes the documentation out-dated:
>>>
>>> https://github.com/ilbers/isar/blob/master/doc/user_manual.md#getting-started
>>>
>>>
>>>
>>> Should I expect updated for user_manual?
>>
>> The user manual is widely outdated already, and we are about to change
>> further fundamental aspects of Isar (proper wic integration, multistrap
>> removal, ...). Let's wait for that to finish, then rewrite the manual.
>>
> 
> I couldn't agree with such approach. Isar is the community project, so
> at anytime new users could appear, keeping out-dated documentation or
> even invalid one, makes the whole project unusable. Also I suppose in
> near future we will be in permanent "about to change fundamentals".
> It would be nice to define who and when will document new features, so
> the new official release could be announced.

I generally agree, but - as I said - the manual was already outdated
prior to all the recent changes. That was the reason I didn't care
updating it.

Again, it would be best to redesign the manual once all the upcoming key
user-visible changes have been send and merged. And those are IMHO

- wic
- image generation (internally via debootstrap, externally via some
  bbclass or include)
- refactoring of meta-isar to meta-isar-example

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-02-19 12:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16  8:52 [PATCH 0/8] Assorted patches Jan Kiszka
2018-02-16  8:52 ` [PATCH 1/8] Mount devtmpfs read-only into chroot Jan Kiszka
2018-02-19 10:09   ` Consolidate mounting in tasks (was Re: [PATCH 1/8] Mount devtmpfs read-only into chroot) Claudius Heine
2018-02-20  6:38   ` [PATCH 1/8] Mount devtmpfs read-only into chroot Alexander Smirnov
2018-02-20  7:02     ` Alexander Smirnov
2018-02-20  7:03     ` Jan Kiszka
2018-02-20  8:18       ` Claudius Heine
2018-02-16  8:52 ` [PATCH 2/8] isar-events: Wait for failing umounts Jan Kiszka
2018-02-19  9:45   ` Alexander Smirnov
2018-02-19  9:48     ` Jan Kiszka
2018-02-19 10:03       ` Alexander Smirnov
2018-02-19 11:10         ` Jan Kiszka
2018-02-16  8:52 ` [PATCH 3/8] isar-events: Do not match on distro and arch Jan Kiszka
2018-02-19  9:54   ` Alexander Smirnov
2018-02-19 11:08     ` Jan Kiszka
2018-02-16  8:52 ` [PATCH 4/8] Add Debian arm64 support to the core Jan Kiszka
2018-02-16  8:52 ` [PATCH 5/8] Add qemuarm64-stretch multiconfig Jan Kiszka
2018-02-19 10:23   ` Alexander Smirnov
2018-02-19 11:15     ` Jan Kiszka
2018-02-19 12:19       ` Alexander Smirnov
2018-02-19 12:36         ` Jan Kiszka [this message]
2018-02-16  8:52 ` [PATCH 6/8] Add qemuarm64-stretch to CI Jan Kiszka
2018-02-16  8:52 ` [PATCH 7/8] build-kernel.sh: Add copyright header Jan Kiszka
2018-02-16  8:52 ` [PATCH 8/8] Enhance credits Jan Kiszka
2018-02-19 13:56 ` [PATCH 0/8] Assorted patches Alexander Smirnov
2018-02-19 14:08   ` Jan Kiszka
2018-02-19 14:19     ` Alexander Smirnov
2018-02-20 11:19 ` Alexander Smirnov

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=131fdcc4-1030-c8b5-7404-b93ddbe8d2aa@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=asmirnov@ilbers.de \
    --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