From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gui-libs/eglexternalplatform/
Date: Fri, 26 Mar 2021 15:55:00 +0000 (UTC) [thread overview]
Message-ID: <1616774089.11b2a059445e840a62385d696935c9207ce7a2d4.sam@gentoo> (raw)
commit: 11b2a059445e840a62385d696935c9207ce7a2d4
Author: Ionen Wolkens <sudinave <AT> gmail <DOT> com>
AuthorDate: Wed Mar 24 18:22:28 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 26 15:54:49 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=11b2a059
gui-libs/eglexternalplatform: drop ALLARCHES
While this compiles/test nothing, when stabilized together with
egl-wayland it could reveal arch-specific issues in this package
and on second thought shouldn't be allarches.
Signed-off-by: Ionen Wolkens <sudinave <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
gui-libs/eglexternalplatform/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/gui-libs/eglexternalplatform/metadata.xml b/gui-libs/eglexternalplatform/metadata.xml
index d4e22d4e34e..c7865d8e5e2 100644
--- a/gui-libs/eglexternalplatform/metadata.xml
+++ b/gui-libs/eglexternalplatform/metadata.xml
@@ -9,7 +9,6 @@
<email>proxy-maint@gentoo.org</email>
<name>Proxy Maintainers</name>
</maintainer>
- <stabilize-allarches/>
<upstream>
<remote-id type="github">NVIDIA/eglexternalplatform</remote-id>
</upstream>
next reply other threads:[~2021-03-26 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 15:55 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-04 2:56 [gentoo-commits] repo/gentoo:master commit in: gui-libs/eglexternalplatform/ Ionen Wolkens
2024-09-03 12:31 Ionen Wolkens
2024-08-02 15:59 Ionen Wolkens
2024-07-23 15:15 Ionen Wolkens
2022-02-14 0:48 Sam James
2021-12-24 14:28 Ionen Wolkens
2021-04-17 14:44 David Seifert
2021-04-17 14:44 David Seifert
2021-03-21 15:53 David Seifert
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=1616774089.11b2a059445e840a62385d696935c9207ce7a2d4.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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