From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Cc: javier.viguera@digi.com
Subject: Re: Dylan backports
Date: Thu, 10 Oct 2013 21:31:27 +0200 [thread overview]
Message-ID: <20131010213127.14c4f478@e6520eb> (raw)
In-Reply-To: <5256CE06.60502@digi.com>
Hi Javier,
Le Thu, 10 Oct 2013 17:55:50 +0200,
Javier Viguera <javier.viguera@digi.com> a écrit :
> Bear with me if this has been already replied, but what is the procedure
> to get patches applied in maintenance branches (e.g. dylan)?
>
> I sent a couple of patches some time ago:
>
> <http://patchwork.openembedded.org/patch/57455/>
> <http://patchwork.openembedded.org/patch/57475/>
>
> that fixes broken builds in Dylan, but I'm not sure if this is the
> correct way because at the moment they have not made their way into the
> repo.
>
both pushed to dylan-next for testing.
Thanks
Eric
next prev parent reply other threads:[~2013-10-10 19:31 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 [this message]
2013-11-07 14:50 ` Javier Viguera
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=20131010213127.14c4f478@e6520eb \
--to=eric@eukrea.com \
--cc=javier.viguera@digi.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;
as well as URLs for NNTP newsgroup(s).