From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: "49412@debbugs.gnu.org" <49412@debbugs.gnu.org>
Subject: [bug#49412] [PATCH core-updates] gnu: libdrm: Update to 2.4.107
Date: Thu, 08 Jul 2021 03:02:23 +0000 [thread overview]
Message-ID: <dujRiZjoTmEXJ6uYCwo4_yLZAKX43ZPgvrBFiQq6p_57_aWPLtKhk6OBkrN2cOkyogsFP1JeQ7a6dIbwKiNmnH4Paic4GF29WIldR6do0N4=@protonmail.com> (raw)
In-Reply-To: <QrTifMEQj7NNxMGVSB3sz29sZeuLqUUlFDNq_07vQeyKlKaoXmiohOs_YuwiIbjJ0HQOF7pDsuAlFRXj_8P2khZ480ECUdHw72Hqh5q5Pe4=@protonmail.com>
> If you mean the 'when tests?' patch, then I'd send it to 49412@debbugs.gnu.orgto keep the libdrm patches together (maybe as a v2 patch series). If you mean‘updating mesa to 21.1.1x’, then I'd send that patch to guix-patches@gnu.org,as updating 'mesa' seems much more complicated than only updating 'libdrm'(see reply by John Kehayias).
Just to follow up here, I think Mesa can be updated pretty simply too, as the original Mesa patch referenced also enabled libglvnd. I've followed up on both the original patch submission and on guix-devel (to gather feedback on moving things to libglvnd).
next prev parent reply other threads:[~2021-07-08 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 8:43 [bug#49412] [PATCH core-updates] gnu: libdrm: Update to 2.4.107 Kaelyn Takata via Guix-patches via
2021-07-05 15:15 ` Maxime Devos
2021-07-05 15:58 ` Kaelyn via Guix-patches via
2021-07-06 8:24 ` Maxime Devos
2021-07-05 21:58 ` John Kehayias via Guix-patches via
2021-07-08 3:02 ` John Kehayias via Guix-patches via [this message]
2021-07-08 15:43 ` John Kehayias via Guix-patches via
2021-07-13 16:57 ` [bug#49412] [PATCH v2] " Kaelyn Takata via Guix-patches via
2021-07-26 14:19 ` Thiago Jung Bauermann via Guix-patches via
2021-07-31 10:03 ` bug#49412: [PATCH core-updates] " Ludovic Courtès
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='dujRiZjoTmEXJ6uYCwo4_yLZAKX43ZPgvrBFiQq6p_57_aWPLtKhk6OBkrN2cOkyogsFP1JeQ7a6dIbwKiNmnH4Paic4GF29WIldR6do0N4=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=49412@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.