From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: bitbake-dev <bitbake-dev@lists.berlios.de>
Subject: Re: Bitbake 1.8.2 released!
Date: Mon, 30 Apr 2007 20:48:31 +0200 [thread overview]
Message-ID: <463639FF.80306@dominion.kabel.utwente.nl> (raw)
In-Reply-To: <1177942098.5872.37.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
> On Thu, 2007-04-26 at 16:27 +0200, Koen Kooi wrote:
>> Richard Purdie schreef:
>>> Bitbake 1.8.2 has been released.
>>>
>>> http://prdownload.berlios.de/bitbake/bitbake-1.8.2.tar.gz
>> Do we have a concrete date for the 1.8 changeover already?
>
> Not that I'm aware of. The release was the first step. I'll wait a few
> more days and see what other bugs appear (if any) and then I guess we
> run with the two month changeover.
Everytime I say "works fine over here" someone on IRC pops up with a 1.8 problem, so I'd
better stay quiet :)
> In fact looking at the date, 1st July could be good...
I thought we counted the 2 months since the initial idea (e.g. last month).
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGNjn/MkyGM64RGpERAmRQAJ4zpSg2n4/A44Gn6qORsk7Hyl1TJgCfZI3o
8oThUp+brDRROedYzTE04xw=
=QsdB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-04-30 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 12:06 Bitbake 1.8.2 released! Richard Purdie
2007-04-26 14:27 ` Koen Kooi
2007-04-30 14:08 ` Richard Purdie
2007-04-30 18:48 ` Koen Kooi [this message]
2007-06-08 17:40 ` 3 weeks left till requiring bitbake 1.8.x (was Re: Bitbake 1.8.2 released!) Koen Kooi
2007-07-01 8:37 ` Koen Kooi
2007-07-01 11:22 ` Holger Freyther
2007-07-01 15:30 ` requiring bitbake >= 1.8.5 Koen Kooi
2007-04-26 14:32 ` Bitbake 1.8.2 released! Justin Patrin
2007-04-26 14:32 ` Justin Patrin
2007-04-26 14:51 ` Koen Kooi
2007-04-26 17:24 ` Justin Patrin
2007-04-26 17:38 ` 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=463639FF.80306@dominion.kabel.utwente.nl \
--to=koen@dominion.kabel.utwente.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.