From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 25DBC76294 for ; Sun, 14 Feb 2016 15:18:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u1EFIJC1021970; Sun, 14 Feb 2016 15:18:19 GMT Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uptC8myzjK22; Sun, 14 Feb 2016 15:18:19 +0000 (GMT) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u1EFIGcT021966 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Sun, 14 Feb 2016 15:18:17 GMT Message-ID: <1455463095.16142.412.camel@linuxfoundation.org> From: Richard Purdie To: Christopher Larson , bitbake-devel@lists.openembedded.org Date: Sun, 14 Feb 2016 15:18:15 +0000 In-Reply-To: References: X-Mailer: Evolution 3.16.5-1ubuntu3.1 Mime-Version: 1.0 Subject: Re: [RFC PATCH 1/1] bb.ui.knotty: prefix task messages with recipe/task X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Feb 2016 15:18:22 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2016-02-12 at 00:15 +0000, Christopher Larson wrote: > On Thu, Feb 11, 2016 at 5:13 PM Christopher Larson > wrote: > > From: Christopher Larson > > > > An example prefix: `perl-5.22.1-r0 do_compile:` > > > > Signed-off-by: Christopher Larson > I realize this may well be something to do for 2.2 rather than 2.1, > but I wanted to throw it out and get thoughts on it, as I'm sick of > manually prefixing our log messages in tasks :) I like the idea and actually wondered why this was an RFC, shouldn't we just do it? Having watched oe-selftest having a problems with this, I can see why we may need to be more cautious :/. Still trying to assess how bad the issues there are. Cheers, Richard