From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE stable, testing, dev
Date: Thu, 19 Aug 2010 11:33:25 +0200 [thread overview]
Message-ID: <4C6CFA65.3000604@kernelconcepts.de> (raw)
In-Reply-To: <AANLkTiknntyGcs6gdHDx84J8m7QufqZ8CPVs4nF5urD7@mail.gmail.com>
Hi,
Cliff Brake schrieb:
>> So something like Debian's stable, testing and unstable[1]?
>
> That sounds good to me -- so how about org.openembedded.dev and
> org.openembedded.testing branches?
great to see this finally happen, I remember we discussed this years ago.
> I'll plan to start doing a clean build of dev every Monday for the
> Beagleboard, and then merge to testing once it builds. Initial
> targets:
>
> Angstrom Distro
> beagleboard/beagleboard-linuxtag2010-demo-image
> x86/minimal-image
I would start to make use of it right now. Starting with builds for armv6 and
armv4t. I would use a different distribution (minimal maybe) for one of the
builds at least to see how this behaves.
> My workstation runs a 64-bit OS, so that is probably worst case
> (compared to i686).
Did you ever build on a PowerPC? :-)
Greetings
Florian
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
http://www.kernelconcepts.de/en
next prev parent reply other threads:[~2010-08-19 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 15:07 OE stable, testing, dev (was Re: What to do about the poor bitbake Quality Control?) Cliff Brake
2010-08-18 16:11 ` Jason Kridner
2010-08-18 17:05 ` Frans Meulenbroeks
2010-08-20 0:02 ` Denys Dmytriyenko
2010-08-21 5:53 ` Esben Haabendal
2010-08-23 8:45 ` Koen Kooi
2010-08-18 17:15 ` Khem Raj
2010-08-19 9:33 ` Florian Boor [this message]
2010-08-21 6:26 ` Frans Meulenbroeks
2010-08-21 12:31 ` Gary Thomas
2010-08-23 16:59 OE stable, testing, dev Cliff Brake
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=4C6CFA65.3000604@kernelconcepts.de \
--to=florian.boor@kernelconcepts.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 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.