From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] neard: upgrade to 0.10
Date: Mon, 18 Mar 2013 16:13:33 +0000 [thread overview]
Message-ID: <1363623213.16482.57.camel@ted> (raw)
In-Reply-To: <20130318151612.GC13277@jama.dyndns-home.com>
On Mon, 2013-03-18 at 16:16 +0100, Martin Jansa wrote:
> On Mon, Mar 18, 2013 at 03:53:42PM +0100, Olivier Guiter wrote:
> > neard ver 0.10:
> > Added initial WiFi handover support.
> > Added Service Name Lookup support to nfctool.
> > Added NDEF building unit tests.
> > Added State support to Bluetooth handover agent.
> > Added neard and neard.conf man pages.
> > Added a copy of the NFC kernel header.
> > Fixed handover validation tests failures.
> > Fixed Tag and Device PropertyChanged signal.
> >
> > Signed-off-by: Olivier Guiter <olivier.guiter@linux.intel.com>
> > ---
> > meta/recipes-connectivity/neard/neard_0.9.bb | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/meta/recipes-connectivity/neard/neard_0.9.bb b/meta/recipes-connectivity/neard/neard_0.9.bb
> > index 8e33a9d..3ece002 100644
> > --- a/meta/recipes-connectivity/neard/neard_0.9.bb
> > +++ b/meta/recipes-connectivity/neard/neard_0.9.bb
> > @@ -47,14 +47,14 @@ FILES_${PN}-dbg += "${libdir}/${BPN}/*/.debug"
> >
> > RDEPENDS_${PN}-tests = "python python-dbus python-pygobject"
> >
> > -# This is valid for 0.9+
> > +# This is valid for 0.10+
> > LIC_FILES_CHKSUM = "file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e \
> > file://src/near.h;beginline=1;endline=20;md5=358e4deefef251a4761e1ffacc965d13 \
> > "
> > S = "${WORKDIR}/git"
> > -SRCREV = "1e20e396cb837017b7e5ef822bfdab6ce060d2cf"
> > -PV = "0.9-git${SRCPV}"
> > -PR = "r1"
> > +SRCREV = "eb486bf35e24d7d1db61350f5ab393a0c880523d"
> > +PV = "0.10-git${SRCPV}"
>
> This should be "+git${SCREV}" PV increment is good time to fix
> that without need for PE bump.
Whilst I agree, this has been useful for finding some bugs in the way
some of the version replacement code works...
Cheers,
Richard
prev parent reply other threads:[~2013-03-18 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 14:53 [PATCH] neard: upgrade to 0.10 Olivier Guiter
2013-03-18 15:16 ` Martin Jansa
2013-03-18 15:34 ` [PATCH v2] " Olivier Guiter
2013-03-18 16:13 ` Richard Purdie [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=1363623213.16482.57.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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