From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyproject-metadata/
Date: Thu, 13 Jun 2024 05:18:24 +0000 (UTC) [thread overview]
Message-ID: <1718255830.47d2f857bb7fa5f9a8133b6ca2d3a98dbc7a1e1e.sam@gentoo> (raw)
commit: 47d2f857bb7fa5f9a8133b6ca2d3a98dbc7a1e1e
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 13 05:17:10 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 13 05:17:10 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=47d2f857
dev-python/pyproject-metadata: mark ALLARCHES
Bug: https://bugs.gentoo.org/931174
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pyproject-metadata/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/pyproject-metadata/metadata.xml b/dev-python/pyproject-metadata/metadata.xml
index c80fb93700e8..26e6b1cdb733 100644
--- a/dev-python/pyproject-metadata/metadata.xml
+++ b/dev-python/pyproject-metadata/metadata.xml
@@ -4,6 +4,7 @@
<maintainer type="project">
<email>python@gentoo.org</email>
</maintainer>
+ <stabilize-allarches/>
<upstream>
<remote-id type="github">pypa/pyproject-metadata</remote-id>
<remote-id type="pypi">pyproject-metadata</remote-id>
next reply other threads:[~2024-06-13 5:18 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 5:18 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-29 9:13 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyproject-metadata/ Michał Górny
2025-03-29 7:59 Arthur Zamarin
2025-03-11 8:47 Michał Górny
2025-02-16 14:14 Michał Górny
2024-11-09 9:50 Sam James
2024-10-26 11:52 Michał Górny
2024-10-23 6:16 Michał Górny
2024-10-22 3:10 Michał Górny
2024-10-12 7:28 Michał Górny
2024-10-08 3:00 Michał Górny
2024-10-05 4:58 Michał Górny
2024-10-01 4:24 Michał Górny
2024-09-28 7:42 Michał Górny
2024-09-28 7:42 Michał Górny
2024-09-21 7:41 Michał Górny
2024-09-14 6:03 Michał Górny
2024-09-13 13:47 Michał Górny
2024-06-13 10:31 Michał Górny
2024-06-13 5:18 Sam James
2024-05-13 18:45 Michał Górny
2024-05-04 9:48 Arthur Zamarin
2024-05-04 7:59 Arthur Zamarin
2024-05-04 7:55 Arthur Zamarin
2024-05-04 7:47 Arthur Zamarin
2024-05-04 7:30 Sam James
2024-05-04 7:28 Arthur Zamarin
2024-05-04 7:28 Arthur Zamarin
2024-04-18 5:34 Michał Górny
2024-04-17 13:23 Michał Górny
2024-04-15 12:19 Michał Górny
2024-03-26 20:17 Ionen Wolkens
2023-08-24 21:42 James Le Cuirot
2023-08-24 18:09 Arthur Zamarin
2023-08-02 4:27 Sam James
2023-06-02 11:54 Arthur Zamarin
2023-03-04 14:44 Michał Górny
2023-03-04 7:24 Arthur Zamarin
2023-03-04 5:29 Arthur Zamarin
2023-03-03 19:38 Arthur Zamarin
2023-03-03 17:41 Arthur Zamarin
2023-03-03 17:27 Arthur Zamarin
2023-01-31 7:09 Michał Górny
2022-11-14 9:24 Arthur Zamarin
2022-11-14 3:46 Michał Górny
2022-11-12 16:31 Arthur Zamarin
2022-10-25 8:07 Sam James
2022-10-25 8:07 Sam James
2022-10-24 6:37 Agostino Sarubbo
2022-10-23 7:52 Agostino Sarubbo
2022-10-23 7:52 Agostino Sarubbo
2022-10-23 7:51 Agostino Sarubbo
2022-10-09 16:10 Sam James
2022-10-09 16:10 Sam James
2022-10-09 0:09 Sam James
2022-10-09 0:04 Sam James
2022-08-01 18:08 Arthur Zamarin
2022-07-31 17:12 Arthur Zamarin
2022-07-31 16:05 Jakov Smolić
2022-07-07 8:26 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=1718255830.47d2f857bb7fa5f9a8133b6ca2d3a98dbc7a1e1e.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