All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: Python2.7.2 compatibility
Date: Tue, 17 Jan 2012 09:20:34 +0100	[thread overview]
Message-ID: <8772233880060257226@unknownmsgid> (raw)
In-Reply-To: <CA+M6bX=AwJFueoj1mGOkP2b7pFm14SSpOEMcbU1Ly4B_5v6LLg@mail.gmail.com>

Thanks Tom for the clarification.

Il giorno 16/gen/2012, alle ore 20:28, Tom Rini <tom.rini@gmail.com> ha scritto:

> On Mon, Jan 16, 2012 at 1:00 AM, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
>> Hi All, I've read the OE-Classic repository will be stopped and alla the
>> new work will be on OE-Core one. Can you confirm this? If so, I'll have to
>> move my work on a given layer in this new developing tree. Please let me
>> know.
>
> While the exact timetable isn't set in stone, yes, this is the long
> stated plan.  For work that's already in-flight, as it were, there'll
> be the 2011.03-maintenance branch for as long as there's interest but
> the oe-core model is where the project is heading for the future.
>
> --
> Tom
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2012-01-17  8:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f13d827.8b7a0e0a.2808.ffffe10eSMTPIN_ADDED@mx.google.com>
2012-01-16  8:00 ` Python2.7.2 compatibility Giuseppe Condorelli
2012-01-16 19:18   ` Tom Rini
2012-01-17  8:20     ` Giuseppe Condorelli [this message]
2011-12-28 15:43 Giuseppe Condorelli
2011-12-28 15:48 ` Paul Eggleton
2011-12-28 16:57   ` Giuseppe Condorelli
2011-12-28 17:02     ` Chris Larson
2011-12-28 17:04     ` Paul Eggleton

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=8772233880060257226@unknownmsgid \
    --to=giuseppe.condorelli@gmail.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 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.