From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6750187537661165568 X-Received: by 2002:a19:7602:: with SMTP id c2mr1197530lff.118.1574182598710; Tue, 19 Nov 2019 08:56:38 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:b4e2:: with SMTP id s2ls5540061ljm.4.gmail; Tue, 19 Nov 2019 08:56:38 -0800 (PST) X-Google-Smtp-Source: APXvYqxkiTlA1UoHN8TOsOWbSh3Yf5Ei8JHEQxvp3luz+k0h1eTC2sbUTms7SejudJIoxwzlUm1S X-Received: by 2002:a2e:970a:: with SMTP id r10mr4934702lji.142.1574182598320; Tue, 19 Nov 2019 08:56:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574182598; cv=none; d=google.com; s=arc-20160816; b=pq4uAIQu1R/YwcCpdbb5qDwnIuR6TQScjM+X4REWx5xWaUk1pc6bbuVKlmrNeuuMqJ 9+4XZMN48z0osmsfJJZtWBcMsQdnoYkg54Pi2/aHgZmR+NzRhM7+KwFZnlBmKt4Kpns0 maksgZH0vO0c8wGStFz2fZUdlzTRCCCzqAB7suxUAnapy7UeeFED24ZbJs9bNsQqCNBJ bggkak1tGZ7nt1gltTKr9rcvECGCNNXp8LoSKqG3ZxyTncWrFjwaCIq3fzBLNUYrMvaM pjUWU3u905jDD3hBZixc6UQeIN60EVmVmWnZ8SepvVfJ2g/1vWZS0Xm703HAEhJP6O0R nqkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=AoY5iTudaUeqb4VOpdijB1HbbcAzPyAyjVDJRfnQwbA=; b=0JkXT7DJ0ybYznOTu5Z6nbGa/cyU5qRLL9TciVTF/AC9lREJV8+WBRja0DggZlLG0n Yu7+2JFljrWy6KhRQxodZvkFsrN5+sDKd6EYX7BG/0wv3pMu3K5e78p47/ht1rRNkRCC poyBZ2nvGRKWO8f5cTZGV9awpYSMCVNsX725DwtvhvHmvHbXf18XeKc9tjJEGlfqGpUT R8PbhV5ZB81vsBxle0mI6I9ZpjVBW9NPpInyC88Nal9vlDuUIYvcb68FZ0EndMxywXkY MFCyXAxXotI8vsHh1fh09XaApmRSikXqx2yZ9S6HmZx2CZEOsM+EbqH0MArAhu9Nk/Ui Bu1Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id y23si1067765lfy.5.2019.11.19.08.56.38 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 Nov 2019 08:56:38 -0800 (PST) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id xAJGuaua010079 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 19 Nov 2019 17:56:37 +0100 Date: Tue, 19 Nov 2019 17:56:35 +0100 From: Baurzhan Ismagulov To: isar-users Subject: Re: [PATCH v4 - misc fixes 0/6] miscellaneous (minor) fixes Message-ID: <20191119165635.h7kded3e75p6bk5j@yssyq.m.ilbers.de> Mail-Followup-To: isar-users References: <1572958385-246-1-git-send-email-Cedric_Hombourger@mentor.com> <1573205003-1335-1-git-send-email-Cedric_Hombourger@mentor.com> <9af716d7-f9e4-4745-85b3-cfe4c65ef585@googlegroups.com> <20191114170112.nopfyhugrzc3olqk@yssyq.m.ilbers.de> <8594de25-19a5-44a2-a4c0-cdf3a7b66f21@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8594de25-19a5-44a2-a4c0-cdf3a7b66f21@googlegroups.com> User-Agent: NeoMutt/20180716 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: T/9Qoa0DqsgU On Fri, Nov 15, 2019 at 08:59:15AM -0800, chombourger@gmail.com wrote: > Rebased locally (it did apply cleanly for me) - will anyway send v5 Yes, I've seen this behavior -- rebase is fine, git am fails. Usually that was due the changes in the context lines (git am is possibly pickier than rebase for whatever reason), but in this case I couldn't identify any changes in the context lines, either. > I can check what upstream does but to answer the other question, clean > unfortunately leaves them behind Isar -- yes, I had checked. The question was about the Yocto clean. Just in case anyone has an answer. > WICTMP is created with mktemp -d so I wonder if we would have to store it > somewhere if we wanted to keep files in the buildchroot > but delete them when we run do_clean > > should we introduce WIC_DEBUG?= "0" and keep them if it was set to "1"? To make it clear, overall I'm willing to apply the series as is in v4. I'll check v5 and let you know. I had thought about WIC_DEBUG, but I think it isn't worth the effort. We don't modify the file, so having copies is useful only for rare cases. OTOH, it eats space and the user might not be aware of that. > that sounds like a good idea but do we want to expand the scope of this > patch series? No, I'd also like to avoid expanding the scope. > As an aside, do we have a central TODO list where we can record things we > really want to > get done before we release something like 1.0? I recall seeing e-mails from > different people > with own lists. Should we have it in the repo so it's easy to find? We used to have it. We've removed it after a discussion here and possibly offline. Some issues have been moved to GitHub. Feel free to create new issues there. With kind regards, Baurzhan.