From: "Burton, Ross" <ross.burton@intel.com>
To: Anuj Mittal <anuj.mittal@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] libva-utils: upgrade to 2.0.0
Date: Mon, 5 Feb 2018 14:50:43 +0000 [thread overview]
Message-ID: <CAJTo0LYjqJd5K5q7_Xie--URMSzqagSpRLrJaPk+6N2kBTrC6w@mail.gmail.com> (raw)
In-Reply-To: <1517811692-28225-3-git-send-email-anuj.mittal@intel.com>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
On 5 February 2018 at 06:21, Anuj Mittal <anuj.mittal@intel.com> wrote:
> -SRC_URI = "git://github.com/01org/libva-utils.git;branch=v1.8-branch"
> -SRCREV = "011c709b98b52db3b10aeb361dfea9da43930364"
> -UPSTREAM_CHECK_URI = "https://github.com/01org/libva-utils/releases"
> +SRC_URI = "git://github.com/intel/libva-utils.git"
> +SRCREV = "505216d0e0d30273f665c888d4c60aa694060729"
> +UPSTREAM_CHECK_URI = "https://github.com/intel/libva-utils/releases"
> UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>(\d+(\.\d+)+))"
>
There are proper tarballs available on the github site too now:
https://github.com/intel/libva-utils/releases/download/2.0.0/libva-utils-2.0.0.tar.bz2
<https://github.com/intel/libva-utils/releases/download/2.0.0/libva-utils-2.0.0.tar.bz2>Can
you switch this to use those instead?
Ross
[-- Attachment #2: Type: text/html, Size: 1893 bytes --]
next prev parent reply other threads:[~2018-02-05 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 6:21 [PATCH 1/3] maintainers.inc: update ownership Anuj Mittal
2018-02-05 6:21 ` [PATCH 2/3] libva: upgrade to 2.0.0 Anuj Mittal
2018-02-05 14:51 ` Burton, Ross
2018-02-05 6:21 ` [PATCH 3/3] libva-utils: " Anuj Mittal
2018-02-05 14:50 ` Burton, Ross [this message]
2018-02-05 6:33 ` ✗ patchtest: failure for "maintainers.inc: update owners..." and 2 more Patchwork
2018-02-05 6:45 ` Anuj Mittal
2018-02-05 9:07 ` [PATCH 1/3] maintainers.inc: update ownership Maxin B. John
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=CAJTo0LYjqJd5K5q7_Xie--URMSzqagSpRLrJaPk+6N2kBTrC6w@mail.gmail.com \
--to=ross.burton@intel.com \
--cc=anuj.mittal@intel.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 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.