From: Richard Purdie <rpurdie@rpsys.net>
To: bitbake-dev@lists.berlios.de
Cc: openembedded-devel <openembedded-devel@openembedded.org>
Subject: Bitbake release
Date: Sat, 06 Dec 2008 14:39:36 +0000 [thread overview]
Message-ID: <1228574376.5375.6.camel@dax.rpnet.com> (raw)
Hi,
As people have probably noticed I just synced up a number of useful
changes from Poky into bitbake and brought things pretty much back into
sync.
The current plan is to let this stabilise for 1 week and the providing
no major bugs were introduced, make a new release (finally!).
Could people therefore upgrade to latest bitbake-1.8 from svn and report
any problems please.
For reference, we will probably make OE.dev depend on the new bitbake
version pretty rapidly allowing some cleanups and optimisation unless
there are any strong objections.
Cheers,
Richard
--
Richard Purdie
Intel Open Source Technology Centre
next reply other threads:[~2008-12-06 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 14:39 Richard Purdie [this message]
2008-12-06 15:32 ` Bitbake release Koen Kooi
2008-12-06 17:50 ` Tom Rini
2008-12-06 18:23 ` Koen Kooi
2008-12-06 22:13 ` Paul Sokolovsky
2008-12-06 22:56 ` Richard Purdie
2008-12-08 10:37 ` Koen Kooi
2008-12-16 13:19 ` Holger Freyther
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=1228574376.5375.6.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=bitbake-dev@lists.berlios.de \
--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