public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gui-libs/vte-common/
Date: Sat, 12 Nov 2022 06:01:31 +0000 (UTC)	[thread overview]
Message-ID: <1668232833.8672ac1adbd739c650563fa067b1486fd43bd290.xen0n@gentoo> (raw)

commit:     8672ac1adbd739c650563fa067b1486fd43bd290
Author:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 12 06:00:33 2022 +0000
Commit:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Sat Nov 12 06:00:33 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8672ac1a

gui-libs/vte-common: keyword 0.70.1 for ~loong

Bug: https://bugs.gentoo.org/880237
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>

 gui-libs/vte-common/vte-common-0.70.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gui-libs/vte-common/vte-common-0.70.1.ebuild b/gui-libs/vte-common/vte-common-0.70.1.ebuild
index ab499cfd04ad..e9f0d8683f79 100644
--- a/gui-libs/vte-common/vte-common-0.70.1.ebuild
+++ b/gui-libs/vte-common/vte-common-0.70.1.ebuild
@@ -13,7 +13,7 @@ HOMEPAGE="https://wiki.gnome.org/Apps/Terminal/VTE https://gitlab.gnome.org/GNOM
 LICENSE="LGPL-3+ GPL-3+"
 SLOT="2.91" # vte_api_version in meson.build
 IUSE="systemd"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~sparc"
+KEYWORDS="amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~sparc"
 
 # Upstream is hostile and refuses to upload tarballs.
 SRC_URI="https://gitlab.gnome.org/GNOME/vte/-/archive/${PV}/vte-${PV}.tar.bz2"


             reply	other threads:[~2022-11-12  6:01 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12  6:01 WANG Xuerui [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-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-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=1668232833.8672ac1adbd739c650563fa067b1486fd43bd290.xen0n@gentoo \
    --to=xen0n@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