From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Graphical Corruption on Chromium Apps with Mesa 19.0.5
Date: Tue, 04 Jun 2019 13:30:30 +0200 [thread overview]
Message-ID: <20190604113030.iCEIks5xKvsKS5WKZg4gAy_i5OjipJPy-at2G7P4vHA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
New comment by silvernode on void-packages repository
https://github.com/void-linux/void-packages/issues/11907#issuecomment-498632955
Comment:
Fair enough, hi Juan!
On Tue, Jun 4, 2019, 02:11 Juan RP <notifications@github.com> wrote:
> How hard is to revert the changes and build the packages locally? git and
> xbps-src are our friends.
>
> Three simple commands and you can get back to 19.0.4 or revert the
> affected changes. Not sure why people complain about this.
>
> If you really care that much then go to the mesa bugtracker and complain
> there.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/11907?email_source=notifications&email_token=AADCENEJUHHNXNYL25YUOT3PYYWVFA5CNFSM4HPJ5WS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW36BIA#issuecomment-498589856>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AADCENGRCX2CFJNPBALSOWDPYYWVFANCNFSM4HPJ5WSQ>
> .
>
next prev parent reply other threads:[~2019-06-04 11:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>
2019-05-30 15:30 ` voidlinux-github
2019-05-30 22:15 ` voidlinux-github
2019-06-01 12:10 ` voidlinux-github
2019-06-01 18:56 ` voidlinux-github
2019-06-01 19:20 ` voidlinux-github
2019-06-01 22:00 ` voidlinux-github
2019-06-02 0:23 ` voidlinux-github
2019-06-02 0:26 ` voidlinux-github
2019-06-02 0:29 ` voidlinux-github
2019-06-02 4:11 ` voidlinux-github
2019-06-02 15:32 ` voidlinux-github
2019-06-02 20:55 ` voidlinux-github
2019-06-03 0:21 ` voidlinux-github
2019-06-03 1:36 ` voidlinux-github
2019-06-03 1:42 ` voidlinux-github
2019-06-03 1:44 ` voidlinux-github
2019-06-04 9:05 ` voidlinux-github
2019-06-04 9:11 ` voidlinux-github
2019-06-04 11:30 ` voidlinux-github [this message]
2019-06-04 22:10 ` voidlinux-github
2019-06-04 23:02 ` voidlinux-github
2019-06-06 11:06 ` [ISSUE] [CLOSED] " voidlinux-github
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=20190604113030.iCEIks5xKvsKS5WKZg4gAy_i5OjipJPy-at2G7P4vHA@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).