From: Javier Viguera <javier.viguera@digi.com>
To: "Eric Bénard" <eric@eukrea.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: Dylan backports
Date: Thu, 7 Nov 2013 15:50:22 +0100 [thread overview]
Message-ID: <527BA8AE.4000306@digi.com> (raw)
In-Reply-To: <20131010213127.14c4f478@e6520eb>
Hi Eric, all,
On 10/10/13 21:31, Eric Bénard wrote:
> both pushed to dylan-next for testing.
>
> Thanks
> Eric
I appreciate you included the patches into 'dylan-next' for testing but
it surprises me they are not in *dylan* yet.
Is this normal? I sent the patches a couple of months ago. They were
included for testing almost one month ago and yet they are not in *dylan*.
For the moment i keep the patches as *bbappends* in our own layer, but i
would like to get rid of them once they are included in 'meta-openembedded'.
Thanks for your help.
-
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.
next prev parent reply other threads:[~2013-11-07 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 15:55 Dylan backports Javier Viguera
2013-10-10 19:31 ` Eric Bénard
2013-11-07 14:50 ` Javier Viguera [this message]
2013-11-07 15:14 ` Eric Bénard
2013-11-07 16:02 ` cherokee wrong SRC_URI (was Dylan backports) Javier Viguera
2013-11-07 16:45 ` Paul Eggleton
2013-11-07 17:12 ` Javier Viguera
2013-11-07 18:25 ` 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=527BA8AE.4000306@digi.com \
--to=javier.viguera@digi.com \
--cc=eric@eukrea.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