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: dev-python/python-json-logger/
Date: Mon,  2 Jan 2023 02:26:35 +0000 (UTC)	[thread overview]
Message-ID: <1672625435.8743d0f877503562902c35951a2a35036e038511.xen0n@gentoo> (raw)

commit:     8743d0f877503562902c35951a2a35036e038511
Author:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Mon Jan  2 02:10:35 2023 +0000
Commit:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Mon Jan  2 02:10:35 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8743d0f8

dev-python/python-json-logger: keyword 2.0.4 for ~loong

Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>

 dev-python/python-json-logger/python-json-logger-2.0.4.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/python-json-logger/python-json-logger-2.0.4.ebuild b/dev-python/python-json-logger/python-json-logger-2.0.4.ebuild
index 240f63e2da79..f98dd9c7a559 100644
--- a/dev-python/python-json-logger/python-json-logger-2.0.4.ebuild
+++ b/dev-python/python-json-logger/python-json-logger-2.0.4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -17,6 +17,6 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ia64 ~ppc ~ppc64"
+KEYWORDS="~amd64 ~arm64 ~ia64 ~loong ~ppc ~ppc64"
 
 distutils_enable_tests unittest


             reply	other threads:[~2023-01-02  2:26 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02  2:26 WANG Xuerui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08  7:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-json-logger/ Michał Górny
2025-02-27 10:48 Sam James
2025-01-04 17:26 Sam James
2025-01-04 17:26 Sam James
2025-01-04 13:41 Sam James
2025-01-04 13:37 Arthur Zamarin
2025-01-04 12:03 Sam James
2025-01-04 11:44 Sam James
2024-12-17  4:12 Michał Górny
2024-12-16  5:57 Michał Górny
2024-12-14 19:05 Michał Górny
2024-12-13  6:15 Michał Górny
2024-11-20 11:13 Michał Górny
2024-11-20  9:49 Sam James
2024-07-27  9:28 Arthur Zamarin
2024-07-27  9:08 Arthur Zamarin
2024-07-27  8:35 Arthur Zamarin
2024-07-27  8:30 Arthur Zamarin
2024-07-27  8:19 Arthur Zamarin
2024-07-27  7:35 Arthur Zamarin
2024-07-27  6:44 Arthur Zamarin
2023-10-24 15:39 Michał Górny
2023-03-23  0:43 Sam James
2023-03-16 18:13 Michał Górny
2023-03-15 21:19 Arthur Zamarin
2023-03-15 21:18 Arthur Zamarin
2023-03-11 17:44 Arthur Zamarin
2023-03-11 17:24 Sam James
2023-03-11 16:50 Arthur Zamarin
2023-03-11 16:50 Arthur Zamarin
2023-03-11 16:00 Sam James
2023-03-11 16:00 Sam James
2023-03-04 18:13 Arthur Zamarin
2023-03-04 18:13 Arthur Zamarin
2023-03-04 17:49 Arthur Zamarin
2023-02-22  5:09 Michał Górny
2023-02-15  7:16 Michał Górny
2023-02-15  7:16 Michał Górny
2023-02-13  6:05 Michał Górny
2023-01-04  6:31 Arthur Zamarin
2023-01-03 11:23 Yixun Lan
2022-12-31 11:22 Arthur Zamarin
2022-12-20 23:28 Sam James
2022-12-20 23:28 Sam James
2022-12-20 23:28 Sam James
2022-12-20 19:24 Andrew Ammerlaan

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=1672625435.8743d0f877503562902c35951a2a35036e038511.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