unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dan <i@dan.games>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Branch (and team?) for mesa updates
Date: Sun, 27 Aug 2023 12:45:52 +0800 (GMT+08:00)	[thread overview]
Message-ID: <999619d0-78b5-48dc-89c6-5ab9fc30b275@dan.games> (raw)
In-Reply-To: <87il92iq4b.fsf@protonmail.com>

Hi John,

Aug 26, 2023 08:51:49 John Kehayias <john.kehayias@protonmail.com>:
>
>
> Though at least (gnu packages gl) looks pretty
> reasonable to start for maybe a graphics team? Maybe with vulkan?
>
> I'm still not sure but I should probably propose something concrete
> with at least myself for gl since those patches generally will go to
> the mesa-updates branch for convenient building.
>
> Anyone else want in?

I use vulkan and sdl2 for my day to day development, and I once submitted 
a patch series updating various vulkan packages.  I'm interested in 
maintaining these vulkan packages and I like the idea of having a 
graphics team.  Meanwhile, I'm not so sure if the team should be 
responsible for sdl2, but I would like to discuss the possibility first.


  parent reply	other threads:[~2023-08-31 18:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 16:12 Branch (and team?) for mesa updates John Kehayias
2023-07-31  1:50 ` Maxim Cournoyer
2023-08-26  0:50   ` John Kehayias
2023-08-26 19:52     ` Maxim Cournoyer
2023-08-27  4:45     ` dan [this message]
2023-09-07 18:45       ` Tobias Platen
  -- strict thread matches above, loose matches on Subject: below --
2023-06-30 15:56 John Kehayias
2023-06-19 18:25 John Kehayias
2023-07-02 10:30 ` Andreas Enge
2023-07-05 15:47   ` Katherine Cox-Buday
2023-07-05 18:08     ` Andreas Enge
2023-07-05 20:12       ` 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=999619d0-78b5-48dc-89c6-5ab9fc30b275@dan.games \
    --to=i@dan.games \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=maxim.cournoyer@gmail.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).