From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: dan <i@dan.games>
Cc: 66964@debbugs.gnu.org
Subject: [bug#66964] Request for merging "mesa-updates" branch
Date: Tue, 14 Nov 2023 20:05:50 +0000 [thread overview]
Message-ID: <8734x8umli.fsf_-_@protonmail.com> (raw)
In-Reply-To: <87a5rr32x8.fsf@protonmail.com>
Hi dan,
On Thu, Nov 09, 2023 at 09:43 PM, dan wrote:
> Hi John,
>
> I noticed one of my commit #65153 is on the mesa-update branch, it
> would be helpful if you could take a look at #65155, an update trying
> to export XDG_DATA_DIRS for mesa. Since no one replied there, I'm not
> sure if this change is appropriate and if it fits in this update.
Apologies I did not see this message as I think you only sent it to the
bug number (which does not get sent to anyone else as far as I know). I
had meant to respond to #65155 but I think I forgot. I did have a note
on the thread on guix-devel about this briefly:
> I don't think this is a correct change as written (search-path should
> be in vulkan-loader if I'm understanding what is supposed to happen
> here). Anyway, will follow up on that issue and left it out for now.
I'll follow up on that bug number directly to discuss.
Sorry for the miscommunication!
John
next prev parent reply other threads:[~2023-11-14 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 4:45 [bug#66964] Request for merging "mesa-updates" branch John Kehayias via Guix-patches via
2023-11-09 13:43 ` dan
2023-11-14 20:05 ` John Kehayias via Guix-patches via [this message]
[not found] <878r7b32qm.fsf@protonmail.com>
2023-11-12 20:01 ` [bug#66964] mesa-updates: call for patches Kaelyn via Guix-patches via
[not found] ` <87y1f0t7s9.fsf_-_@protonmail.com>
2023-11-15 6:28 ` [bug#66964] Request for merging "mesa-updates" branch Efraim Flashner
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=8734x8umli.fsf_-_@protonmail.com \
--to=guix-patches@gnu.org \
--cc=66964@debbugs.gnu.org \
--cc=i@dan.games \
--cc=john.kehayias@protonmail.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.
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).