From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gui-libs/vte-common/
Date: Thu, 26 Oct 2023 16:12:28 +0000 (UTC) [thread overview]
Message-ID: <1698336683.81ca37814fc92debf111d099986b9a1d6339e398.pacho@gentoo> (raw)
commit: 81ca37814fc92debf111d099986b9a1d6339e398
Author: Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 26 16:10:12 2023 +0000
Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Thu Oct 26 16:11:23 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=81ca3781
gui-libs/vte-common: drop ALLARCHES
vte-urlencode-cwd is not suitable for ALLARCHES
Closes: https://bugs.gentoo.org/912166
Thanks-to: Agostino Sarubbo
Signed-off-by: Pacho Ramos <pacho <AT> gentoo.org>
gui-libs/vte-common/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/gui-libs/vte-common/metadata.xml b/gui-libs/vte-common/metadata.xml
index ca243d09d328..a75f3f473b80 100644
--- a/gui-libs/vte-common/metadata.xml
+++ b/gui-libs/vte-common/metadata.xml
@@ -5,7 +5,6 @@
<email>gnome@gentoo.org</email>
<name>Gentoo GNOME Desktop</name>
</maintainer>
- <stabilize-allarches/>
<use>
<flag name="systemd">Support moving terminal child processes to their own systemd user scopes to avoid terminal getting killed due to child causing OOM</flag>
</use>
next reply other threads:[~2023-10-26 16:12 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 16:12 Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-09 19:27 [gentoo-commits] repo/gentoo:master commit in: gui-libs/vte-common/ Patrick McLean
2024-08-09 10:12 Pacho Ramos
2024-08-09 9:54 Pacho Ramos
2024-03-07 23:51 Sam James
2024-02-11 14:21 Mart Raudsepp
2024-02-11 8:09 Arthur Zamarin
2024-02-11 8:09 Arthur Zamarin
2024-02-11 6:01 Sam James
2024-02-11 3:39 Sam James
2023-12-19 18:36 Pacho Ramos
2023-11-29 4:23 Sam James
2023-10-26 16:12 Pacho Ramos
2023-09-22 17:18 Matt Turner
2023-08-18 10:52 Sam James
2023-08-16 22:32 Matt Turner
2023-07-16 20:31 Matt Turner
2023-07-15 11:43 Arthur Zamarin
2023-07-02 11:18 Sam James
2023-07-02 11:18 Sam James
2023-07-02 8:33 Sam James
2023-07-02 8:33 Sam James
2023-07-02 8:33 Sam James
2023-07-02 8:04 Sam James
2023-06-05 16:46 Matt Turner
2023-05-03 3:53 Sam James
2023-05-02 19:37 Arthur Zamarin
2023-05-02 19:16 Sam James
2023-05-02 19:09 Arthur Zamarin
2023-05-02 17:51 Arthur Zamarin
2023-05-02 17:42 Arthur Zamarin
2023-05-02 17:27 Arthur Zamarin
2023-04-17 0:42 Matt Turner
2023-04-10 12:39 Matt Turner
2023-04-01 19:03 Arthur Zamarin
2023-04-01 19:01 Arthur Zamarin
2023-03-31 12:04 Arthur Zamarin
2023-03-30 17:44 Arthur Zamarin
2023-03-19 3:58 Matt Turner
2023-02-11 20:48 Matt Turner
2023-01-27 20:45 Matt Turner
2022-12-22 11:13 Arthur Zamarin
2022-12-17 6:45 Arthur Zamarin
2022-12-16 20:57 Arthur Zamarin
2022-12-16 20:37 Arthur Zamarin
2022-12-16 20:30 Arthur Zamarin
2022-12-02 21:53 Matt Turner
2022-11-21 17:07 Joonas Niilola
2022-11-14 6:53 Arthur Zamarin
2022-11-12 6:01 WANG Xuerui
2022-11-10 0:33 Yixun Lan
2022-11-10 0:19 Matt Turner
2022-11-09 14:11 Matt Turner
2022-11-09 14:11 Matt Turner
2022-11-09 14:11 Matt Turner
2022-11-07 23:18 Sam James
2022-11-07 7:26 Sam James
2022-10-30 23:21 Matt Turner
2022-10-25 15:25 Matt Turner
2022-09-26 16:00 Matt Turner
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=1698336683.81ca37814fc92debf111d099986b9a1d6339e398.pacho@gentoo \
--to=pacho@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