From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: webhob@yoctoproject.org
Cc: "Dragomir, CalinX L" <calinx.l.dragomir@intel.com>,
"Zhang, Jessica" <jessica.zhang@intel.com>
Subject: Re: [Webhob] task types and outcomes
Date: Fri, 31 May 2013 15:02:40 +0100 [thread overview]
Message-ID: <4494389.ENWZ8JdZbF@helios> (raw)
In-Reply-To: <CAP9ODKoZmi=XXLa-7OA-fB1=A9SQ7U_NTUcHHWyxPFyraa3MuQ@mail.gmail.com>
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" <richard.purdie@linuxfoundation.org>
> >
> > 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
next prev parent reply other threads:[~2013-05-31 14:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 16:16 [Webhob] task types and outcomes Barros Pena, Belen
2013-05-28 16:24 ` Paul Eggleton
2013-05-28 17:17 ` Barros Pena, Belen
2013-05-29 15:57 ` Paul Eggleton
2013-05-29 21:39 ` Richard Purdie
2013-05-30 10:57 ` Barros Pena, Belen
2013-05-30 13:10 ` Dragomir, CalinX L
2013-05-30 13:51 ` Barros Pena, Belen
2013-05-30 14:28 ` Richard Purdie
2013-05-31 11:49 ` Barros Pena, Belen
2013-05-31 12:48 ` Damian, Alexandru
2013-05-31 13:18 ` Barros Pena, Belen
2013-05-30 14:21 ` Richard Purdie
2013-05-31 13:50 ` Barros Pena, Belen
2013-05-31 13:53 ` Otavio Salvador
2013-05-31 14:02 ` Paul Eggleton [this message]
2013-05-31 14:04 ` Dragomir, CalinX L
2013-06-03 12:32 ` Barros Pena, Belen
2013-06-05 10:40 ` Barros Pena, Belen
2013-06-05 11:23 ` Dragomir, CalinX L
2013-06-05 17:14 ` [Webhob] Django models Paul Eggleton
2013-06-06 9:27 ` Calin Dragomir
2013-06-06 11:06 ` Barros Pena, Belen
2013-06-06 12:54 ` Paul Eggleton
2013-06-07 11:04 ` Barros Pena, Belen
2013-06-07 11:52 ` [Webhob] Django models wiki updates Calin Dragomir
2013-06-12 11:03 ` Damian, Alexandru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4494389.ENWZ8JdZbF@helios \
--to=paul.eggleton@linux.intel.com \
--cc=calinx.l.dragomir@intel.com \
--cc=jessica.zhang@intel.com \
--cc=webhob@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.