From: Ricardo Wurmus <rekado@elephly.net>
To: 58617@debbugs.gnu.org
Subject: [bug#58617] [PATCH core-updates 0/8] Update Vulkan packages to sdk-1.3.224.1.
Date: Fri, 30 Dec 2022 10:51:41 +0100 [thread overview]
Message-ID: <87h6xd6wxp.fsf@elephly.net> (raw)
In-Reply-To: <20221019003957.31382-1-kaelyn.alexi@protonmail.com>
Hi Kaelyn,
my apologies for the delay in reviewing this.
I’m a little confused about this. Is this the follow-up to issue
#57297? I see that you closed this issue, but I don’t think it has been
applied yet. Is this still good for core-updates?
Do we still need the work from issue #57297, which is still in the
update-vulkan-headers-staging branch?
I’d appreciate some clarification, so I can make sure your work was not
in vain and gets merged soon.
Thank you!
--
Ricardo
prev parent reply other threads:[~2022-12-30 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 0:40 [bug#58617] [PATCH core-updates 0/8] Update Vulkan packages to sdk-1.3.224.1 Kaelyn Takata via Guix-patches via
2022-10-19 0:41 ` [bug#58617] [PATCH core-updates 1/8] gnu: spirv-headers: Update to 1.3.224.1 Kaelyn Takata via Guix-patches via
2022-10-19 0:42 ` [bug#58617] [PATCH core-updates 2/8] gnu: spirv-tools: Update to 2022.3 Kaelyn Takata via Guix-patches via
2022-10-19 0:42 ` [bug#58617] [PATCH core-updates 3/8] gnu: spirv-cross: Update to 1.3.224.1 Kaelyn Takata via Guix-patches via
2022-10-19 0:42 ` [bug#58617] [PATCH core-updates 4/8] gnu: vulkan-headers: " Kaelyn Takata via Guix-patches via
2022-10-19 0:42 ` [bug#58617] [PATCH core-updates 5/8] gnu: vulkan-loader: " Kaelyn Takata via Guix-patches via
2022-10-19 0:42 ` [bug#58617] [PATCH core-updates 6/8] gnu: vulkan-tools: " Kaelyn Takata via Guix-patches via
2022-10-19 0:42 ` [bug#58617] [PATCH core-updates 7/8] gnu: shaderc: Update to 2022.2 Kaelyn Takata via Guix-patches via
2022-10-19 0:42 ` [bug#58617] [PATCH core-updates 8/8] gnu: Add vulkan-validationlayers Kaelyn Takata via Guix-patches via
2022-12-30 9:51 ` Ricardo Wurmus [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6xd6wxp.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=58617@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).