From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 0F513E01409 for ; Fri, 31 May 2013 07:02:43 -0700 (PDT) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 31 May 2013 07:02:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,779,1363158000"; d="scan'208";a="346190352" Received: from unknown (HELO helios.localnet) ([10.252.121.185]) by fmsmga002.fm.intel.com with ESMTP; 31 May 2013 07:02:41 -0700 From: Paul Eggleton To: webhob@yoctoproject.org Date: Fri, 31 May 2013 15:02:40 +0100 Message-ID: <4494389.ENWZ8JdZbF@helios> Organization: Intel Corporation User-Agent: KMail/4.10.2 (Linux/3.8.0-22-generic; KDE/4.10.2; i686; ; ) In-Reply-To: References: <1369923685.14887.300.camel@ted> MIME-Version: 1.0 Cc: "Dragomir, CalinX L" , "Zhang, Jessica" Subject: Re: [Webhob] task types and outcomes X-BeenThere: webhob@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 14:02:43 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Friday 31 May 2013 10:53:43 Otavio Salvador wrote: > On Fri, May 31, 2013 at 10:50 AM, Barros Pena, Belen < > > belen.barros.pena@intel.com> wrote: > > On 30/05/2013 15:21, "Richard Purdie" > > > > wrote: > > >> So for the 'all tasks' table, we could have a 'task type' column > > >> classifying tasks as 'executed' and 'not executed'. > > > > > >I'd prefer "Prebuilt" than "not executed" but yes. > > > > Prebuilt sounds good to me, but it causes a bit of a naming issue. We have > > identified 3 possible 'Outcomes' for prebuilt tasks: sstate, skipped and > > previously built (tasks for which an stamp file exists). 'Prebuilt' and > > 'Previously built' are too similar, which is bound to cause confusion. > > > > Does any of you have any ideas for a better name for the 'Previously > > built' outcome? > > What about 'Cached'? That clashes with the sstate "cache". Not that I have any better suggestion... Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre