From: "Eric Bénard" <eric@eukrea.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Meta-OpenEmbedded - Dylan maintenance
Date: Mon, 22 Apr 2013 22:14:15 +0200 [thread overview]
Message-ID: <20130422221415.1e88893e@e6520eb> (raw)
In-Reply-To: <CAP9ODKrT9eS6pYhUnW1JgqJL3b9cevdYAiH-WLTLBhSuQuEy3Q@mail.gmail.com>
Hi Otavio,
Le Mon, 22 Apr 2013 16:08:55 -0300,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> The upcoming release of dylan is very close and we should start think
> about its maintenance; is someone intending to be the maintainer of
> the 'dylan' branch of meta-oe?
>
I can continue maintenance with dylan as experience of the switch from
denzil to danny showed that n-1 gets very few updates once n is
released (and as my BSP are switching to dylan next month ;-).
Best regards,
Eric
next prev parent reply other threads:[~2013-04-22 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 19:08 Meta-OpenEmbedded - Dylan maintenance Otavio Salvador
2013-04-22 20:14 ` Eric Bénard [this message]
2013-04-22 21:23 ` Martin Jansa
2013-04-22 21:39 ` Otavio Salvador
2013-04-22 21:50 ` Andreas Müller
2013-04-26 7:33 ` Eric Bénard
2013-04-26 7:33 ` Eric Bénard
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=20130422221415.1e88893e@e6520eb \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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