From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6450015460633083904 X-Received: by 10.46.87.78 with SMTP id r14mr63476ljd.29.1503405919975; Tue, 22 Aug 2017 05:45:19 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.44.143 with SMTP id s137ls755530lfs.29.gmail; Tue, 22 Aug 2017 05:45:18 -0700 (PDT) X-Received: by 10.46.71.5 with SMTP id u5mr64142lja.2.1503405918121; Tue, 22 Aug 2017 05:45:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1503405918; cv=none; d=google.com; s=arc-20160816; b=0ZgpjFDm0wG9k/wcunmLkknnXpf5c4fQP1FrJbUvoZDWssJ2mLEnP0LuOjqpqwAZYE IzpBzGF/lu62dcMKFZ5Xxv26LaiuHEiesVWqgMoQgpg2N2bBc0x/GI6zDHpsKltmCrpw K7H0DRqFoqZU5/IGXK2+GvT2Qur9A8W7u/OURz0BCHcZOLbYtl08q3aKiU3rTprDPaaV 68BZyEuW7YhIKqb3v0wqoVwhT/ywITkpI09B25kdY2LJAw9mQik/xj243N8Ig3W95xI/ lw+qIVBOO9mKs51iDMySq1cU1BF38NIJbonCUSj6tnE9bZXWpJqlaHu8fnF6lXcbh+yF FFoQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=HA8IOtSmcmfV9LqXGuDbvZ8+tzo7u3L7wOeJexH/kd8=; b=J3m91dRgoHAVXCcGeUmOK4Siip4ijq5aTXxjBt/lyInxwMYyQLLfxqaJKPI77kbZfY WoHPQU8j1pqgMVZb2MKSMrtK8Xg69KxdKNDg035FVhS7pc3An4vKHyDBJMkbe08cCLxk zbK3lXNsrnGcmCGHQr6DBEwehhbmh7ECAB5t0PD85x1uwabpBrL0vMBqujNKEhgJSBAt lh9su+ij8N5HkcbxWYZ5xYx0IG5LX5g2n8DPtAKrHqU50ikgwLZyZ7lIR6zUa6j83TVC ipqsxrO7FSzkB7qAK8HlOVlFnRr/52VG7oePZDB1en9Gj3+WPc9WeHOFUXqGXB+vQrKL qanw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id k84si3355774wmh.5.2017.08.22.05.45.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Aug 2017 05:45:18 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id v7MCjHdN022290 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 22 Aug 2017 14:45:17 +0200 Received: from md1em3qc ([139.25.68.40]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id v7MCjHmg019409; Tue, 22 Aug 2017 14:45:17 +0200 Date: Tue, 22 Aug 2017 14:45:28 +0200 From: Henning Schild To: Baurzhan Ismagulov Cc: Subject: Re: [PATCH 0-10 of 16 v2 4/8] meta: conf: use bitbake.conf from bitbake and apply local changes Message-ID: <20170822144528.37e1cf5e@md1em3qc> In-Reply-To: <20170822113129.GF4244@yssyq.radix50.net> References: <20170821132539.GD8387@yssyq.radix50.net> <20170821202940.2f4b43c6@md1em3qc> <20170822113129.GF4244@yssyq.radix50.net> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: 7POiE9tIrgjW Am Tue, 22 Aug 2017 13:31:29 +0200 schrieb Baurzhan Ismagulov : > On Mon, Aug 21, 2017 at 08:29:40PM +0200, Henning Schild wrote: > > > (2) is worse, as IMHO, bitbake should do that itself and it > > > doesn't (https://github.com/ilbers/isar/issues/27). Concatenating > > > configs is magic that Yocto users do not expect, and this has to > > > be documented. Could you provide a patch for the manual? > > > > No. You do not apply a patch directly to master if that creates an > > issue, you could have asked me for a v3 instead. Please revert or > > provide the patch to the manual yourself. > > In general, this is our intended approach (although in this > particular case I'd still not block the inclusion of a patch that has > value for the project by a required bitbake change upstream -- but > that is a different story). Our current focus is to work together to > improve Isar and process the patch backlog -- which I thought you > agreed with Alex on phone. If this doesn't help you and you prefer > the other model -- let's do it that way, it will only save my time. We agreed that he would change my patches to save me the time to rebase and change them. I asked him to add his signed-off to all patches he actually modifies. After that offer i did not hear back about remaining issues, so i assumed they all got fixed on your side. And now "my commits" are the cause for issues ... If you see the issue coming you should bring it up in the review and not after applying the patch. I further assumed that any such patch would naturally be published for review again, which did not happen or at least the comments where ignored. Henning > With kind regards, > Baurzhan. >