Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: SCM fetched recipes without a SRCREV - e.g. libgee-native
Date: Wed, 21 Oct 2009 13:10:28 +0200	[thread overview]
Message-ID: <1256123428.14897.18.camel@opal> (raw)
In-Reply-To: <200910211303.49278.holger+oe@freyther.de>

> 1.) bitbake -cfetchall task
> 
> then remove network and
> 
> 2.) bitbake task...
> 
> if that is not the case we suck.

Agreed. Perhaps it's really time to add some git commit checks as things
like the presence of a SRCREV_pn entry in sane-srcrev.inc can easily be
checked.

:M:





  reply	other threads:[~2009-10-21 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 10:47 SCM fetched recipes without a SRCREV - e.g. libgee-native Koen Kooi
2009-10-21 11:03 ` Holger Hans Peter Freyther
2009-10-21 11:10   ` Michael 'Mickey' Lauer [this message]
2009-10-21 11:21     ` Koen Kooi
2009-10-21 11:42       ` Michael 'Mickey' Lauer
2009-10-21 18:57         ` Richard Purdie
2009-10-22  0:59           ` Denys Dmytriyenko
2009-10-22  8:44             ` Richard Purdie
2009-10-21 11:15   ` Robert P. J. Day

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=1256123428.14897.18.camel@opal \
    --to=mickey@vanille-media.de \
    --cc=openembedded-devel@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