public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/funcparserlib/
Date: Sat, 10 Dec 2022 08:57:05 +0000 (UTC)	[thread overview]
Message-ID: <1670662609.c3b8707b7789678d6e5ba3a7b7c847c397cbedba.arthurzam@gentoo> (raw)

commit:     c3b8707b7789678d6e5ba3a7b7c847c397cbedba
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 10 08:56:49 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Dec 10 08:56:49 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c3b8707b

dev-python/funcparserlib: Stabilize 1.0.1 ALLARCHES, #885163

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-python/funcparserlib/funcparserlib-1.0.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/funcparserlib/funcparserlib-1.0.1.ebuild b/dev-python/funcparserlib/funcparserlib-1.0.1.ebuild
index 332f7b6a5ad9..2648fecf740c 100644
--- a/dev-python/funcparserlib/funcparserlib-1.0.1.ebuild
+++ b/dev-python/funcparserlib/funcparserlib-1.0.1.ebuild
@@ -17,7 +17,7 @@ SRC_URI="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ppc ppc64 ~riscv ~s390 sparc x86"
 
 BDEPEND="
 	test? (


             reply	other threads:[~2022-12-10  8:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10  8:57 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-16 19:56 [gentoo-commits] repo/gentoo:master commit in: dev-python/funcparserlib/ Petr Vaněk
2023-06-06 17:39 Arthur Zamarin
2022-12-10  9:06 Michał Górny
2022-12-10  9:03 Michał Górny
2022-11-04  8:23 Arthur Zamarin
2022-05-27 19:45 Michał Górny
2022-05-27  9:07 Jakov Smolić
2022-05-02 19:17 Arthur Zamarin
2022-04-30  7:35 Michał Górny
2022-04-26  3:07 Sam James
2022-04-25 12:11 Michał Górny
2022-02-27 18:46 Michał Górny
2022-01-26 23:19 Michał Górny
2022-01-08 13:35 Michał Górny
2022-01-08 13:32 Arthur Zamarin
2021-12-08 17:08 Arthur Zamarin
2021-10-09 19:25 Arthur Zamarin
2021-10-09 19:18 Sam James
2021-10-09  9:32 Arthur Zamarin
2021-09-10  6:52 Arthur Zamarin
2021-09-10  6:52 Arthur Zamarin
2021-07-27 23:11 Marek Szuba
2021-05-10 19:43 Michał Górny
2021-02-22 22:20 Sam James
2021-02-22 22:20 Sam James
2020-11-30 21:12 Sergei Trofimovich
2020-11-26 19:08 Sam James
2020-11-26 13:21 Sam James
2020-10-07  1:02 Sam James
2020-10-01 17:29 Sergei Trofimovich
2020-09-28 17:41 Sergei Trofimovich
2020-09-27  6:42 Matt Turner
2020-09-13  4:55 Sam James
2020-08-25 10:23 Sam James
2020-08-20 21:55 Sergei Trofimovich
2020-08-18 21:53 Sergei Trofimovich
2020-03-25 13:00 Michał Górny
2020-03-25 13:00 Michał Górny
2020-02-05 13:24 Michał Górny
2019-12-02 21:13 Aaron Bauman
2019-07-14 12:27 Michał Górny
2019-07-14 12:27 Michał Górny
2019-07-14 12:27 Michał Górny
2019-04-27 11:49 Anthony G. Basile
2019-03-16 23:17 Anthony G. Basile
2018-02-05 21:54 Michał Górny
2017-04-22 10:18 Michał Górny

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=1670662609.c3b8707b7789678d6e5ba3a7b7c847c397cbedba.arthurzam@gentoo \
    --to=arthurzam@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