Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: OE Staging ABI Change Warning
Date: Mon, 03 Mar 2008 15:43:10 +0100	[thread overview]
Message-ID: <fqh2pu$7po$1@ger.gmane.org> (raw)
In-Reply-To: <1204554867.8095.61.camel@dax.rpnet.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Purdie schreef:

| I know angstrom is doing some kind of autobuilds but I don't know to
| what extent or what policies govern what is built.

The autobuilders run contrib/angstrom/build-*.sh on a regular interval
and sepukku.bbclass takes care of the reporting. I'd like to work on
improving that, but can't since my bugzilla privs disappeared under
suspicious circumstances....

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHzA5+MkyGM64RGpERArv6AJ4tFkk5b8AcFjpOPbQTXlKkZhr/uACgi2At
8CELjgaM4amqZvAkBG/soAM=
=WDhm
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-03-03 15:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 16:46 OE Staging ABI Change Warning Richard Purdie
2008-02-29 17:24 ` Leon Woestenberg
2008-02-29 18:04   ` Richard Purdie
2008-02-29 18:29     ` Leon Woestenberg
2008-02-29 22:43       ` Richard Purdie
2008-03-03  1:07 ` Holger Freyther
2008-03-03  9:37   ` Richard Purdie
2008-03-03 12:12     ` Holger Freyther
2008-03-03 12:46       ` Koen Kooi
2008-03-03 14:34         ` Richard Purdie
2008-03-03 14:43           ` Koen Kooi [this message]
2008-03-03 15:46           ` Rod Whitby
2008-03-03 16:14             ` Leon Woestenberg
2008-03-03 16:39               ` Leon Woestenberg
2008-03-03 17:20 ` Mike (mwester)
2008-03-04  0:08 ` Koen Kooi
2008-03-04 16:53 ` Koen Kooi
2008-03-06 12:42   ` Richard Purdie
2008-03-06 12:58     ` Koen Kooi

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='fqh2pu$7po$1@ger.gmane.org' \
    --to=koen@dominion.kabel.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