From: Efraim Flashner <efraim@flashner.co.il>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: Josselin Poiret <dev@jpoiret.xyz>, Z572 <zhengjunjie@iscas.ac.cn>,
73288@debbugs.gnu.org
Subject: [bug#73288] Request for merging "mesa-updates" branch
Date: Tue, 5 Nov 2024 12:35:33 +0200 [thread overview]
Message-ID: <Zyn09bwxpJgBFGOf@3900XT> (raw)
In-Reply-To: <87r07q9uz2.fsf@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Tue, Nov 05, 2024 at 04:15:54AM +0000, John Kehayias wrote:
> Yes, sounds good. I did a rebase and deleted/pushed to mesa-updates. I'll check in about 12 hours and will do the merge assuming it still looks good and no sudden issues.
As expected, no change in the derivation for
aarch64/armhf/riscv64/ppc64le
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-05 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 2:38 [bug#73288] Request for merging "mesa-updates" branch John Kehayias via Guix-patches via
2024-09-23 5:34 ` Efraim Flashner
2024-09-30 0:11 ` John Kehayias
2024-10-02 20:53 ` Sharlatan Hellseher
2024-10-03 8:56 ` Steve George via Guix-patches
2024-10-04 8:21 ` Ludovic Courtès
2024-10-03 9:01 ` Steve George via Guix-patches
2024-10-19 14:43 ` [bug#73288] Advance in queue Andreas Enge
2024-10-31 19:35 ` [bug#73288] Request for merging "mesa-updates" branch Sharlatan Hellseher
2024-11-03 10:04 ` Z572
2024-11-03 13:02 ` Efraim Flashner
2024-11-04 2:32 ` John Kehayias via Guix-patches via
2024-11-04 16:50 ` Z572
2024-11-05 4:15 ` John Kehayias via Guix-patches via
2024-11-05 10:35 ` Efraim Flashner [this message]
2024-11-05 18:49 ` bug#73288: " John Kehayias via Guix-patches via
2024-11-04 9:33 ` [bug#73288] " Christopher Baines
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=Zyn09bwxpJgBFGOf@3900XT \
--to=efraim@flashner.co.il \
--cc=73288@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=john.kehayias@protonmail.com \
--cc=zhengjunjie@iscas.ac.cn \
/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.