From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Barnabás Béres" <beresbarnus03@gmail.com>,
romulasry <romulasry@protonmail.com>
Cc: 44558@debbugs.gnu.org
Subject: bug#44558: Mesa isn't update to date
Date: Wed, 11 Nov 2020 13:24:48 +0100 [thread overview]
Message-ID: <87k0ushyi7.fsf@nckx> (raw)
In-Reply-To: <CAOcmTtcMwk85h+ftZsVp=X6hERtXXdvrhuhBDV-kRMfAu=QnVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
Hullo!
Barnabás Béres 写道：
> I think this email went to the wrong place, because you only
> sent a "bug
> report" not a patch. I think it's better to send these kind of
> things to
> bug-guix@gnu.org
Does your mail client mark it as a patch? Strange. I've deleted
the original, but bug-guix@ delivered the list copy to my inbox
and I don't see ‘patches’ in the header.
That said, it's not really a bug report either, or the bug is
missing...
Romulasry, are you suffering from specific Mesa 20.0.7 problems
that 20.2.2 might fix? Please let us know. An otherwise working
package not being at the latest upstream version isn't a bug.
romulasry via Bug reports for GNU Guix 写道：
> Mesa 20.2.2 is released
The core-updates branch updates Mesa to 20.1.9. Would you like to
submit a (tested) core-updates patch updating it to 20.2.2?
> Also it would be nice to see it built with lllvm 11
Same for this! All help is appreciated.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-11-11 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 20:29 bug#44558: Mesa isn't update to date romulasry via Bug reports for GNU Guix
2020-11-11 11:40 ` Barnabás Béres
2020-11-11 12:24 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-11-11 13:08 ` Barnabás Béres
2020-11-11 13:25 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-11 13:55 ` Barnabás Béres
2020-11-12 16:26 ` Guillaume Le Vaillant
2020-11-12 21:27 ` Marius Bakke
2020-11-13 13:56 ` Guillaume Le Vaillant
2020-11-13 15:49 ` Marius Bakke
2021-11-14 1:26 ` Maxim Cournoyer
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=87k0ushyi7.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=44558@debbugs.gnu.org \
--cc=beresbarnus03@gmail.com \
--cc=me@tobias.gr \
--cc=romulasry@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).