unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Branch (and team?) for mesa updates
Date: Fri, 30 Jun 2023 15:56:09 +0000	[thread overview]
Message-ID: <87mt0h6j1s.fsf@protonmail.com> (raw)

On Thu, Jun 29, 2023 at 12:09 PM, John Kehayias wrote:

[snip]
>
> I'll open a branch merge request issue later today as per new
> procedure for QA. Though I believe that only builds 2 branches, which
> is occupied at the moment. Or can someone set a separate build job
> specifically for mesa-updates, especially if we think it is a good
> idea to have this going forward?
>

Merging request for "mesa-updates" branch created:
<https://issues.guix.gnu.org/64369>

>> Do we want a "Mesa team" or something a bit larger? Not sure what
>> exactly, since "graphics" is perhaps too broad. Happy to help
>> spearhead the Mesa front for Guix (the very package that got me first
>> involved in the patching process).
>>
>
> This is still a good question I think, of how we want to have a
> team(s) to handle things like xorg, wayland, mesa, and related
> packages. They are a bit all over the place in terms of scope and what
> they touch. For now I'd like to go ahead with a regular mesa-updates
> branch since that sees regular releases and is pretty self-contained
> currently.
>
> Thanks!
> John



             reply	other threads:[~2023-06-30 15:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 15:56 John Kehayias [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2023-09-07 18:45       ` Tobias Platen
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=87mt0h6j1s.fsf@protonmail.com \
    --to=john.kehayias@protonmail.com \
    --cc=guix-devel@gnu.org \
    /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).