From: "Eric Bénard" <eric@eukrea.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][dylan][PATCH 1/1] x264: fix SRCREV after upstream repository change
Date: Thu, 31 Jul 2014 20:01:18 +0200 [thread overview]
Message-ID: <20140731200118.597e78e6@e6520eb> (raw)
In-Reply-To: <2463245.SkJkBSUsEE@peggleto-mobl5.ger.corp.intel.com>
Hi Paul,
Le Wed, 30 Jul 2014 12:28:42 +0100,
Paul Eggleton <paul.eggleton@linux.intel.com> a écrit :
>
> On Monday 09 June 2014 17:24:30 Paul Eggleton wrote:
> > The upstream x264 project has re-imported all of their old history,
> > meaning that all of the hashes have changed. Update SRCREV based on the
> > mapping list they have provided at:
> >
> > http://sprunge.us/dGOU
> >
> > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > ---
> > meta-oe/recipes-multimedia/x264/x264_git.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta-oe/recipes-multimedia/x264/x264_git.bb
> > b/meta-oe/recipes-multimedia/x264/x264_git.bb index c767ffd..4da24cc 100644
> > --- a/meta-oe/recipes-multimedia/x264/x264_git.bb
> > +++ b/meta-oe/recipes-multimedia/x264/x264_git.bb
> > @@ -11,7 +11,7 @@ DEPENDS = "yasm-native"
> > SRC_URI = "git://git.videolan.org/x264.git \
> > file://don-t-default-to-cortex-a9-with-neon.patch \
> > "
> > -SRCREV = "1cffe9f406cc54f4759fc9eeb85598fb8cae66c7"
> > +SRCREV = "bfed708c5358a2b4ef65923fb0683cefa9184e6f"
> >
> > PV = "r2230+git"
>
> ping
>
pushed, thanks and sorry for the delay
Eric
prev parent reply other threads:[~2014-07-31 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 16:24 [meta-oe][dylan][PATCH 0/1] x264 SRCREV fix Paul Eggleton
2014-06-09 16:24 ` [meta-oe][dylan][PATCH 1/1] x264: fix SRCREV after upstream repository change Paul Eggleton
2014-07-30 11:28 ` Paul Eggleton
2014-07-31 18:01 ` Eric Bénard [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=20140731200118.597e78e6@e6520eb \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 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.