From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6523072403514327040 X-Received: by 10.80.134.135 with SMTP id r7mr4127659eda.1.1519042789906; Mon, 19 Feb 2018 04:19:49 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.169.98 with SMTP id m31ls4052719edc.0.gmail; Mon, 19 Feb 2018 04:19:49 -0800 (PST) X-Google-Smtp-Source: AH8x22779xlkMVekW1BrrM0+s548Sk4WAjd5+f1w1HcoIkRvUYrX0oenMRgVukSHYrRHv5rVDawQ X-Received: by 10.80.202.201 with SMTP id f9mr4172705edi.12.1519042789249; Mon, 19 Feb 2018 04:19:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519042789; cv=none; d=google.com; s=arc-20160816; b=UuQ7K3q9SSjeET0YlEH5CWXc5KaQg9U7UInuHuYwyzGq82sBBYXDzu1gi+ZQj8jpWW UlDc95LGSplbDSdfeRL1UINEC8tR/WzKqVmYEKvzQePOz/FBBcYdfHhvdfk5B3BCDz1+ /F0S2fEHhahsMMA7w6Rg3gw6bNAHlT2m1ok+zpYurkCwCffTQGtP1KvHL5cl3pDYX507 LLHPyjjuyoZjGGW2vWe0BaC1mLDynv8K/Vvu1HmpYXvGTbLBPMSTY5Jb0HEuOWsmCfxC wXI9R6dsT+bEuoO27UknHKpO8U5BytXtxDcBFMKyqw2Z7rqIkvFJWQlMg+6bUJFbljG2 Yh4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=er/Ds6Ykuk2ZCBVU9qbzVTmVKdk6dJ756ylUIaYTlpQ=; b=T6Up3kV1uymMX2D48SGzDdhGWYNF+Ktj4pjpMhbCQEptPBSUGsDsV9fh+Iftot+gRT fH8fri4Isp0FfopzQGwz8WzWwkvnxF7U3tvpa9TB7TaLGVqiAL5PQvhUAhPOqem3ihJG Q6tOdugTAmsn/HRtAax+ko9r1/UdK0BwWneLyQkT1vlXl5JCbfBLwO/jalUV4Jv6iEsY 9JeXOxIRTfpzYdCoOO9sEDzjtZ4kNPmCr8bhTk0qC1xD++gQLK8sCDCq0Zo4a93ZFdEG 8tziGD4p53ecfucV3XcAQA1gnaCnpfVoXKi6mkadsZJtH5GYaRaUlbl0BRvL4rv7cjoF 1HKg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id t4si451600edt.2.2018.02.19.04.19.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Feb 2018 04:19:49 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] ([188.227.110.165]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w1JCJj08031533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 19 Feb 2018 13:19:47 +0100 Subject: Re: [PATCH 5/8] Add qemuarm64-stretch multiconfig To: Jan Kiszka , isar-users References: <32c61c30-ec42-793f-a562-cb5e9b1e6dfa@siemens.com> From: Alexander Smirnov Message-ID: <11c0b40e-c34e-bcb6-0f98-c24999e2f3a1@ilbers.de> Date: Mon, 19 Feb 2018 15:19:40 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <32c61c30-ec42-793f-a562-cb5e9b1e6dfa@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: EqRTaVzpz4iL 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 >>> >>> 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. Alex