From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6450015460633083904 X-Received: by 10.223.174.225 with SMTP id y88mr130954wrc.24.1503488792043; Wed, 23 Aug 2017 04:46:32 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.9.13 with SMTP id 13ls525323ljj.50.gmail; Wed, 23 Aug 2017 04:46:31 -0700 (PDT) X-Received: by 10.25.44.6 with SMTP id s6mr258427lfs.20.1503488791489; Wed, 23 Aug 2017 04:46:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1503488791; cv=none; d=google.com; s=arc-20160816; b=w34Vi9P9PWG21l9/mlT2mRtj5A9ft4VP/NI02vElQ74vcUhpArGrWjeS202DnkQUe/ W5RqFyHptonXXpfrpiEmryjS5zIAJUuuAxRtDjzbcQe8BOCjkCYI3Aga8dUzB9sxdcTT JmjvLD8pRMxfRoXByzf0uq5mxodPO03odUzDYPXFf9w2tOKKJwD9b/LT2Bg14/JfY07m mcpUdoIMd5SKA6KoMKcFhe3Je6XCC9eHMIMg9+McFT91bTb3wEue+gpZ+JTrFwcFMUvB 9NcLubNyN9CMpp6Gb9HoR8JscKjdlM3I/kBXoii2kaEK2nTVjYaAZ9yOL1c/TJYpwV/6 Vp0Q== 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=/oV0D9xKwASiSBqTjZ9q1cxVm8pUxSPDffss6IApwkA=; b=o2biNJRptiqoj9CrgChEDO0sRP5MCx0ucNd4IHXaugOUFvSfQGun9sh728ct1qs77k OD42KTH6n+w38qqqyPJpIhEQCWBmzXIyCZichmJhwj9erQ8eyTJLEFgUZrjPZmVE7G4b HMNM7/cVYDeZvdaJpGwEH1lkPv3IVIX9ncY1sY+dvyHgs3GcegtW/tmCjYY/XNBMN2EY mmUM8ZuF3jHpRCLY6ChCrTJrgFvwHqfEO8sCN6BoptoTWRsjkD/iNp/BSzsAgzCdd7UR Mo3wsZVHi7UwgSvCK9BHj25nFpt1gOTP/jzNZOXUMmtHK0VpE3Wc4R4axIMkiM0w2YQw Zb0A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.2 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 thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id 2si260763wms.6.2017.08.23.04.46.31 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Aug 2017 04:46:31 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.2 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.2 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id v7NBkUmB004281 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 23 Aug 2017 13:46:31 +0200 Received: from md1em3qc ([139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id v7NBkU8T012240; Wed, 23 Aug 2017 13:46:30 +0200 Date: Wed, 23 Aug 2017 13:46:30 +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: <20170823134630.5cbc574a@md1em3qc> In-Reply-To: <20170823113142.GB5580@yssyq.radix50.net> References: <20170821132539.GD8387@yssyq.radix50.net> <20170821202940.2f4b43c6@md1em3qc> <20170822113129.GF4244@yssyq.radix50.net> <20170822144528.37e1cf5e@md1em3qc> <20170822153102.GG4244@yssyq.radix50.net> <20170822205554.690876ef@md1em3qc> <20170823113142.GB5580@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: EERNESx8pIJY Am Wed, 23 Aug 2017 13:31:42 +0200 schrieb Baurzhan Ismagulov : > On Tue, Aug 22, 2017 at 08:55:54PM +0200, Henning Schild wrote: > > Ok, understood. I think using issues as reminder list might shine > > the wrong light on the project, but that is a personal feeling. > > This is a good point. At least small stuff like two lines of docs > would really be better to do immediately and not to postpone. > > Bigger stuff like upstream bitbake changes would still exist. One > approach could be to distinguish between user bugs and project own > TODOs (not offered by GitHub). We've discussed this with Alex; ATM, > we'd prefer to stick to the existing infrastructure, at least till > the development is streamlined. Internally, we have an even longer > list of issues and plan to move them to GitHub for now as well. > > > > We can proceed in this way or stick to the original plan. Or use one > > where both sides modify the patches, depending on the change that > > needs to be made. > > But if anyone substancially changes a patch it has to be reviewed > > again. > > The original plan was supposed to be faster due to quick fixes > without later review. Since we want a final review of changes, let's > switch back to the classic process. > > > > Or at least end up in "the official" next branch where it will > > sit for a few days for everyone to look at. > > Ok, we've discussed this with Alex and would like to introduce next. > > Currently, we are checking whether we still need asmirnov/next, and > what implications that would have on the maintainer process. > > > We also have some wishes: > > * When submitting patches, considering the stuff from CONTRIBUTING > would help us to review them, especially w.r.t. communicating the > background / motivation / intention to work at something early in the > process. Sure, now that this document is there. The patches still on the plate appeared before it. > * We'll comment on the desired formatting. CodingStyle is on my TODO. > > * If there is a problem, please articulate expectations; that would > allow us to address them (unlike e.g. just a request to revert). In this very example i did request the revert earlier, with reasoning. And i got tired of repeating myself and mails not beeing read carefully or at all, also not for the first time. > * We've looked at the apt implementations and currently tend towards > the existing one, as it supports binary package caching and is shared > with the Deby project. Regarding reprepro, we'd like to keep it > because dropping it would mean re-implementing that in Isar and > keeping up with possible Debian archive structure changes in the > future. I have no clue what that section is about. If it has anything to do with workflow we can keep discussing it here. If it has impact on the proposed features please discuss it with the patches. Henning > With kind regards, > Baurzhan. >