Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: BB_STAMP_POLICY
Date: Wed, 28 May 2008 15:13:27 +0200	[thread overview]
Message-ID: <g1jlpn$f7f$1@ger.gmane.org> (raw)

FYI:

11:37:33 Koen: is BB_STAMP_POLICY documented somewhere?
11:37:47 Richard Purdie: Not really
11:38:03 Richard Purdie: Takes the values "file" "whitelist" or "full"
11:38:35 Richard Purdie: "file" is the traditional behaviour with stamps 
just checked within a given recipe
11:38:46 Richard Purdie: "full" checks all the dependencies are consistent
11:39:12 Richard Purdie: "whitelist" allows some packages to be excluded 
from the stamp checking basically so packages staging can work




             reply	other threads:[~2008-05-28 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 13:13 Koen Kooi [this message]
2008-06-02 10:35 ` BB_STAMP_POLICY Detlef Vollmann
2008-06-02 11:07   ` BB_STAMP_POLICY Richard Purdie
2008-06-02 22:09     ` BB_STAMP_POLICY Detlef Vollmann
2008-06-02 23:45       ` BB_STAMP_POLICY Richard Purdie
2008-06-03  5:05         ` BB_STAMP_POLICY Detlef Vollmann

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='g1jlpn$f7f$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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