Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Richard Purdie : meta/classes: Update recrdeptask fields for recursive dependency handling changes in bitbake
Date: Wed, 04 Jul 2012 17:59:49 +0100	[thread overview]
Message-ID: <1341421189.19821.0.camel@ted> (raw)
In-Reply-To: <20120704162654.GE15100@jama.jama.net>

On Wed, 2012-07-04 at 18:26 +0200, Martin Jansa wrote:
> On Wed, Jul 04, 2012 at 01:49:32PM +0000, git@git.openembedded.org wrote:
> > Module: openembedded-core.git
> > Branch: master
> > Commit: 8229fb5d7205f5e5b198ab2860fbcc02054476eb
> > URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=8229fb5d7205f5e5b198ab2860fbcc02054476eb
> > 
> > Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Date:   Mon Jul  2 12:27:46 2012 +0000
> > 
> > meta/classes: Update recrdeptask fields for recursive dependency handling changes in bitbake
> > 
> > This also deletes the buildall task since I seen usecases for it.
> 
> Is there a typo in last sentence? :)
> 
> I've seen
> BB_DEFAULT_TASK = "buildall"
> in my local.conf and now it had to go..

Yes, it is a typo, sorry.

If someone can show me a good usecase for it we can add it back but I'm
not seeing one right now...

Cheers,

Richard




      reply	other threads:[~2012-07-04 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120704134932.B766810217@opal>
2012-07-04 16:26 ` [oe-commits] Richard Purdie : meta/classes: Update recrdeptask fields for recursive dependency handling changes in bitbake Martin Jansa
2012-07-04 16:59   ` Richard Purdie [this message]

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=1341421189.19821.0.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox