From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
Cc: Martin Jansa <martin.jansa@gmail.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 2/2] net-snmp: Update to 5.7.2
Date: Wed, 17 Apr 2013 11:28:42 +0100 [thread overview]
Message-ID: <7119347.tG3WeIFq8N@helios> (raw)
In-Reply-To: <20130417102144.GE26007@jama>
On Wednesday 17 April 2013 12:21:44 Martin Jansa wrote:
> On Wed, Apr 17, 2013 at 11:07:17AM +0100, Jack Mitchell wrote:
> > From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
> >
> > - Removed some un-needed patches
> >
> > Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
> > ---
> >
> > .../net-snmp/files/libnl-3-support.patch | 69 -
> > .../net-snmp/files/sync-with-5.7-branch.patch | 19998
> > ------------------- .../recipes-extended/net-snmp/net-snmp_5.7.2.bb |
> > 31 +
> > 3 files changed, 31 insertions(+), 20067 deletions(-)
> > delete mode 100644
> > meta-oe/recipes-extended/net-snmp/files/libnl-3-support.patch delete
> > mode 100644
> > meta-oe/recipes-extended/net-snmp/files/sync-with-5.7-branch.patch
> > create mode 100644 meta-oe/recipes-extended/net-snmp/net-snmp_5.7.2.bb
> Is there reason to keep net-snmp_5.7.1.bb?
>
> If no, then please remove it in the same commit and send with -M.
Also I just tried to "git am" 2/2 on top of master + 1/2 and it failed, not
sure exactly why. (I wanted to see if this would fix the build failure I noted
earlier.)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-04-17 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 10:07 [meta-oe][PATCH 1/2] net-snmp: fix failure when starting on system without pci bus Jack Mitchell
2013-04-17 10:07 ` [meta-oe][PATCH 2/2] net-snmp: Update to 5.7.2 Jack Mitchell
2013-04-17 10:21 ` Martin Jansa
2013-04-17 10:28 ` Paul Eggleton [this message]
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=7119347.tG3WeIFq8N@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jack.mitchell@dbbroadcast.co.uk \
--cc=martin.jansa@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.