From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [STABLE] branch created: stable/2009
Date: Tue, 31 Mar 2009 22:02:56 +0200 [thread overview]
Message-ID: <49D276F0.2060701@gmx.net> (raw)
In-Reply-To: <200903311837.28324.marcin@juszkiewicz.com.pl>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
Hi,
is it possible/allowed to port things into the stable which IMO make its
maintenance easier? E.g. I've just cleaned up the llvm recipes and made
them side by side installable (multiple version). The stable branch
would be more of a burden when these things differ so much from each other.
Apart from that llvm is not used from anything but the llvm-gcc recipes
which I saw and which look not inspiring confidence.
Last but not least I was going to base the Jalimo recipes on that and
then finally move them into OE.
Regards
Robert
Marcin Juszkiewicz schrieb:
> Hi
>
> I would like to announce creation of new branch: stable/2009 in
> OpenEmbedded repository. It was branched few days ago, build tested and
> got some bugfixes which were added to .dev tree (and back to
> stable/2009).
>
> What was in build test? Distro "angstrom-2008.1", machines: qemuarm
> (armv5te), at91sam9263ek (armv5te), beagleboard (armv7a), qemux86 (i586)
> and vortex86sx (486sx). I tested building of next images: console,
> console-base, x11, beagleboard-demo for each of those machines. So far
> only glibc builds were tested, uclibc one is queued.
>
> I also imported BitBake 1.8.12 (last release) into "stable/2009" branch
> as this is minimal stable version which works with this repository.
>
> Feel free to clone and do tests. I will write more later.
>
> Regards,
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]
next prev parent reply other threads:[~2009-03-31 20:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 16:37 [STABLE] branch created: stable/2009 Marcin Juszkiewicz
2009-03-31 17:00 ` Koen Kooi
2009-03-31 17:17 ` Tom Rini
2009-03-31 19:49 ` Marcin Juszkiewicz
2009-04-01 11:42 ` Koen Kooi
2009-04-02 10:49 ` [RFC] more streamlined review procedure, was: " Koen Kooi
2009-04-02 15:31 ` Marco Cavallini
2009-04-02 17:31 ` Koen Kooi
2009-03-31 20:02 ` Robert Schuster [this message]
2009-04-02 9:55 ` Marcin Juszkiewicz
2009-04-01 7:32 ` Marco Cavallini
2009-04-02 10:52 ` Esben Haabendal
2009-04-02 11:25 ` Marcin Juszkiewicz
2009-04-03 16:18 ` Esben Haabendal
2009-04-03 17:51 ` Marcin Juszkiewicz
2009-04-03 23:55 ` Esben Haabendal
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=49D276F0.2060701@gmx.net \
--to=thebohemian@gmx.net \
--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.