From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Plans for OE classic future
Date: Tue, 1 Nov 2011 08:13:18 +0100 [thread overview]
Message-ID: <4EAF9C0E.9030702@nedap.com> (raw)
In-Reply-To: <20111101010055.GU15391@denix.org>
On 11/01/2011 02:00 AM, Denys Dmytriyenko wrote:
> On Tue, Nov 01, 2011 at 01:38:33AM +0100, Ulf Samuelsson wrote:
>> 2011-10-27 14:27, Martin Jansa skrev:
>>> On Thu, Oct 27, 2011 at 01:56:43PM +0200, Henning Heinold wrote:
>>>> On Thu, Oct 27, 2011 at 10:53:13AM +0000, Mats K?rrman wrote:
>>>>> Hi,
>>>>>
>>>>> Are there any plans for new releases and/or maintenance branches of OE
>>>>> classic?
>>>>>
>>>>> BR / Mats
>>>> Hi,
>>>>
>>>> http://cgit.openembedded.org/openembedded/log/?h=org.openembedded.dev
>>>>
>>>> and
>>>>
>>>> http://cgit.openembedded.org/openembedded/log/?h=2011.03-maintenance
>>>>
>>>> Bye Henning
>>> Are you showing that maintenance ibranch is not so old and that only few
>>> things changed in old OE-classic since then? :)
>>>
>>> Afaik: nobody plans to do another release from OE-classic and
>>> oe-core/meta-oe/BSP's/... are veryclose to first release
>> What repository is used for the BSP's ?
> Each BSP in own repository - http://www.openembedded.org/wiki/LayerIndex
>
Does anybody know where the atmel boards are? (at91sam9263ek)
next prev parent reply other threads:[~2011-11-01 7:20 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcyUlp+U2Tnulhz/TiaFJRlWYsvGkw==>
2011-10-27 10:53 ` Plans for OE classic future Mats Kärrman
2011-10-27 11:56 ` Henning Heinold
2011-10-27 12:27 ` Martin Jansa
2011-11-01 0:38 ` Ulf Samuelsson
2011-11-01 1:00 ` Denys Dmytriyenko
2011-11-01 7:13 ` Jaap de Jong [this message]
2011-11-01 10:39 ` Henning Heinold
2011-10-27 17:44 ` Denys Dmytriyenko
2011-10-27 23:56 ` Tom Rini
2011-11-23 20:46 ` Khem Raj
2011-11-23 21:18 ` Frans Meulenbroeks
2011-11-23 21:30 ` Philip Balister
2011-11-26 21:12 ` Bernhard Guillon
2011-11-27 9:15 ` Frans Meulenbroeks
2011-11-23 22:25 ` Khem Raj
2011-11-23 22:42 ` Andreas Oberritter
2011-11-24 8:03 ` Mats Kärrman
2011-11-24 10:23 ` Hauser, Wolfgang (external)
2011-11-24 11:12 ` Otavio Salvador
2011-11-24 11:24 ` Frans Meulenbroeks
2011-11-24 11:37 ` Otavio Salvador
2011-11-24 11:33 ` Paul Menzel
2011-11-24 11:43 ` Otavio Salvador
2011-11-24 17:45 ` Koen Kooi
2011-11-25 5:23 ` Raffaele Recalcati
2011-11-25 7:31 ` Frans Meulenbroeks
2011-11-25 10:45 ` Otavio Salvador
2011-11-25 22:04 ` Tom Rini
2011-11-26 10:57 ` Ulf Samuelsson
2011-11-26 15:20 ` Tom Rini
2011-11-26 15:49 ` Frans Meulenbroeks
2011-11-26 21:36 ` Tom Rini
2011-11-26 22:01 ` Paul Menzel
2011-11-26 22:33 ` Tom Rini
2011-11-26 22:49 ` Paul Menzel
2011-11-27 2:37 ` Tom Rini
2011-11-27 9:46 ` Koen Kooi
2011-11-27 10:12 ` Frans Meulenbroeks
2011-11-27 17:05 ` Tom Rini
2011-11-27 17:25 ` Frans Meulenbroeks
2011-11-27 18:25 ` Tom Rini
2011-11-27 21:58 ` Frans Meulenbroeks
2011-11-28 2:25 ` Tom Rini
2011-11-26 22:37 ` Raffaele Recalcati
2011-11-26 22:44 ` Otavio Salvador
2011-11-27 2:26 ` Tom Rini
2011-11-26 18:53 ` Ulf Samuelsson
2011-11-26 21:47 ` Tom Rini
2011-11-24 11:43 ` Paul Eggleton
2011-11-24 17:47 ` Koen Kooi
2011-11-24 18:15 ` Andreas Oberritter
2011-11-24 9:12 ` Koen Kooi
2011-11-24 9:31 ` Frans Meulenbroeks
2011-11-24 17:06 ` Khem Raj
2011-11-24 17:41 ` Andreas Oberritter
2011-11-24 18:43 ` Otavio Salvador
2011-11-25 13:17 ` Andreas Oberritter
2011-11-25 22:00 ` Tom Rini
2011-11-24 20:33 ` Paul Menzel
2011-11-25 21:43 ` Tom Rini
2011-11-26 16:11 ` Frans Meulenbroeks
2011-11-26 21:43 ` Tom Rini
2011-11-25 21:52 ` Tom Rini
2011-11-26 3:49 ` Denis 'GNUtoo' Carikli
2011-11-26 15:45 ` Frans Meulenbroeks
2011-11-26 16:56 ` Paul Menzel
2011-11-26 21:28 ` Tom Rini
2011-11-27 9:55 ` Frans Meulenbroeks
2011-11-27 17:15 ` Tom Rini
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=4EAF9C0E.9030702@nedap.com \
--to=jaap.dejong@nedap.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox