From: Javier Viguera <javier.viguera@digi.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Dylan backports
Date: Thu, 10 Oct 2013 17:55:50 +0200 [thread overview]
Message-ID: <5256CE06.60502@digi.com> (raw)
Hi all,
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.
With the current status of dylan, cherokee cannot be downloaded (wrong
SRC_URI) and net-snmp fails to build when not using 'systemd':
snmpd.c:459: undefined reference to `netsnmp_sd_listen_fds'
-
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.
next reply other threads:[~2013-10-10 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 15:55 Javier Viguera [this message]
2013-10-10 19:31 ` Dylan backports Eric Bénard
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=5256CE06.60502@digi.com \
--to=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 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.