From: Ricardo Wurmus <rekado@elephly.net>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Mesa out of date (and move to libglvnd?)
Date: Mon, 19 Jul 2021 14:24:30 +0200 [thread overview]
Message-ID: <87czre5w5d.fsf@elephly.net> (raw)
In-Reply-To: <ieuiH7l3G8QoRkR2cozOIb8FBxF7stpGjUrcqGwHqWWWOSJ_1Ct510P8iOzBHrnAl9g7TeSaplO6iZj2BcANWNCF7Y4cuagoFmGsXegJs3w=@protonmail.com>
John Kehayias <john.kehayias@protonmail.com> writes:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Monday, July 12th, 2021 at 11:22 AM, John Kehayias
> <john.kehayias@protonmail.com> wrote:
>
>> Just pinging here. If there are no good reasons not to, I think
>> we should move ahead with getting libdrm and Mesa up to date,
>> with https://issues.guix.gnu.org/49412 and
>> https://issues.guix.gnu.org/49339 We can work on moving to
>> libglvnd as a separate patch series.
>>
>> Anyone have some thoughts or can these be pushed (to
>> core-updates)?
>
> As an update, both the libdrm and Mesa patches are ready. Given
> the work for libglvnd that needs to be done, I think that should
> be on a separate patch series.
>
> Will these updates be merged before the core-updates freeze?
We could also create a new branch to better track how the
mesa/libdrm upgrades affect packages.
--
Ricardo
next prev parent reply other threads:[~2021-07-19 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 2:51 Mesa out of date (and move to libglvnd?) John Kehayias
2021-07-12 15:22 ` John Kehayias
2021-07-17 18:55 ` John Kehayias
2021-07-19 12:24 ` Ricardo Wurmus [this message]
2021-07-27 21:41 ` John Kehayias
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=87czre5w5d.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--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).