From: "Khem Raj" <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] vulkan-headers: Fix upstream branch deletion issue
Date: Tue, 23 Jun 2020 12:46:49 -0700 [thread overview]
Message-ID: <a9fe68d2-b2d0-4ba8-dca8-78dca19ebb6d@gmail.com> (raw)
In-Reply-To: <20200623134150.603584-1-richard.purdie@linuxfoundation.org>
On 6/23/20 6:41 AM, Richard Purdie wrote:
> The upstream branch was deleted but the commit is in master so reference
> that instead.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> meta/recipes-graphics/vulkan/vulkan-headers_1.2.135.0.bb | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-graphics/vulkan/vulkan-headers_1.2.135.0.bb b/meta/recipes-graphics/vulkan/vulkan-headers_1.2.135.0.bb
> index 54cee96cce0..d21c3d62b90 100644
> --- a/meta/recipes-graphics/vulkan/vulkan-headers_1.2.135.0.bb
> +++ b/meta/recipes-graphics/vulkan/vulkan-headers_1.2.135.0.bb
> @@ -5,7 +5,8 @@ SECTION = "libs"
>
> LICENSE = "Apache-2.0"
> LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57"
> -SRC_URI = "git://github.com/KhronosGroup/Vulkan-Headers.git;branch=sdk-1.2.135"
> +# was sdk-1.2.135 branch but it was removed upstream, commit is in master branch though
> +SRC_URI = "git://github.com/KhronosGroup/Vulkan-Headers.git;branch=master"
>
perhaps better to update to SHA of latest tag ?
https://github.com/KhronosGroup/Vulkan-Headers/releases/tag/v1.2.145
> SRCREV = "fb7f9c9bcd1d1544ea203a1f3d4253d0e90c5a90"
>
>
>
>
>
next prev parent reply other threads:[~2020-06-23 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 13:41 [PATCH] vulkan-headers: Fix upstream branch deletion issue Richard Purdie
2020-06-23 14:02 ` ✗ patchtest: failure for " Patchwork
2020-06-23 19:46 ` Khem Raj [this message]
2020-06-23 20:13 ` [OE-core] [PATCH] " Alexander Kanavin
2020-06-23 20:17 ` Khem Raj
2020-06-23 20:32 ` Alexander Kanavin
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=a9fe68d2-b2d0-4ba8-dca8-78dca19ebb6d@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.