From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org,
peter.seebach@windriver.com
Subject: Re: [PATCH 2/2] pseudo: upgrade to 1.8.0
Date: Mon, 04 Jul 2016 13:10:34 +0100 [thread overview]
Message-ID: <1467634234.2767.3.camel@linux.intel.com> (raw)
In-Reply-To: <d1e04a54-0d95-3add-7f29-5bacff43451f@linux.intel.com>
On Mon, 2016-07-04 at 14:36 +0300, Alexander Kanavin wrote:
> On 07/01/2016 10:30 PM, Joshua Lock wrote:
> > * drop patches where the changes exist upstream
> > * fetch from git as no tarball is available for 1.8.0
>
> > diff --git a/meta/recipes-devtools/pseudo/pseudo_1.8.0.bb
> > b/meta/recipes-devtools/pseudo/pseudo_1.8.0.bb
> > new file mode 100644
> > index 0000000..08477ff
> > --- /dev/null
> > +++ b/meta/recipes-devtools/pseudo/pseudo_1.8.0.bb
> > @@ -0,0 +1,14 @@
> > +require pseudo.inc
> > +
> > +SRCREV = "786c6d3813622d18e12d36c4aa722af6a417c8fa"
> > +PV = "1.8.0+git${SRCPV}"
> > +
> > +SRC_URI = "git://git.yoctoproject.org/pseudo \
>
> This commit id refers to version 1.7.5, and version 1.8.0 is not
> tagged
> at all in the git repository. Can you fix that please?
Thanks for catching this, I failed badly at merging some local changes.
I will send a v2 with the correct SRCREV. I'll also see whether I can
convince someone to tag the repo.
Regards,
Joshua
next prev parent reply other threads:[~2016-07-04 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 19:30 [PATCH 1/2] pseudo: drop recipe for old 1.6.7 version Joshua Lock
2016-07-01 19:30 ` [PATCH 2/2] pseudo: upgrade to 1.8.0 Joshua Lock
2016-07-04 11:36 ` Alexander Kanavin
2016-07-04 12:10 ` Joshua G Lock [this message]
2016-07-04 12:14 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2016-07-05 12:18 [PATCH 0/2] Pseudo upgrade Joshua Lock
2016-07-05 12:18 ` [PATCH 2/2] pseudo: upgrade to 1.8.0 Joshua Lock
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=1467634234.2767.3.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.seebach@windriver.com \
/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