From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyghmi/
Date: Mon, 22 Feb 2021 22:20:10 +0000 (UTC) [thread overview]
Message-ID: <1614032384.0a14b4b22a0377e3bea5025245d52f2f8f519757.sam@gentoo> (raw)
commit: 0a14b4b22a0377e3bea5025245d52f2f8f519757
Author: Jakov Smolic <jakov.smolic <AT> sartura <DOT> hr>
AuthorDate: Mon Feb 22 20:49:11 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb 22 22:19:44 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0a14b4b2
dev-python/pyghmi: Mark ALLARCHES
Signed-off-by: Jakov Smolic <jakov.smolic <AT> sartura.hr>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pyghmi/metadata.xml | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/dev-python/pyghmi/metadata.xml b/dev-python/pyghmi/metadata.xml
index 9ae992913b2..d196ca4f8f8 100644
--- a/dev-python/pyghmi/metadata.xml
+++ b/dev-python/pyghmi/metadata.xml
@@ -1,11 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
+ <maintainer type="person">
+ <email>zmedico@gentoo.org</email>
+ <name>Zac Medico</name>
+ </maintainer>
+ <stabilize-allarches/>
<upstream>
<remote-id type="pypi">pyghmi</remote-id>
<remote-id type="github">openstack/pyghmi</remote-id>
</upstream>
- <maintainer type="person">
- <email>zmedico@gentoo.org</email>
- </maintainer>
</pkgmetadata>
next reply other threads:[~2021-02-22 22:20 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 22:20 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-22 7:50 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyghmi/ Michał Górny
2025-02-22 7:50 Michał Górny
2025-02-14 5:19 Michał Górny
2025-02-06 4:10 Michał Górny
2025-02-06 4:10 Michał Górny
2024-09-10 7:06 Michał Górny
2024-09-10 7:06 Michał Górny
2024-08-28 3:43 Michał Górny
2024-06-16 5:21 Michał Górny
2024-06-16 5:21 Michał Górny
2024-04-10 6:15 Michał Górny
2024-03-28 5:55 Michał Górny
2024-02-13 4:27 Michał Górny
2024-01-23 4:39 Michał Górny
2023-11-23 16:52 Arthur Zamarin
2023-11-18 15:48 Michał Górny
2023-11-18 15:47 Michał Górny
2023-10-27 18:02 Michał Górny
2023-10-20 4:42 Michał Górny
2023-08-28 16:53 Michał Górny
2023-08-04 2:42 Michał Górny
2023-07-24 11:33 Michał Górny
2023-04-14 3:59 Michał Górny
2023-04-08 6:08 Michał Górny
2023-03-24 19:06 Arthur Zamarin
2023-03-09 5:58 Michał Górny
2023-02-22 5:09 Michał Górny
2023-01-18 7:34 Michał Górny
2023-01-11 5:14 Michał Górny
2022-12-03 9:09 Michał Górny
2022-11-16 17:21 Michał Górny
2022-11-14 5:05 Michał Górny
2022-09-23 20:06 Arthur Zamarin
2022-09-23 20:06 Arthur Zamarin
2022-09-09 7:23 Arthur Zamarin
2022-09-09 7:23 Arthur Zamarin
2022-09-09 7:23 Arthur Zamarin
2022-07-14 7:31 Michał Górny
2022-06-28 18:49 Arthur Zamarin
2022-06-28 18:49 Arthur Zamarin
2022-06-24 20:32 Arthur Zamarin
2022-06-22 17:31 Arthur Zamarin
2022-06-16 8:08 Michał Górny
2022-06-15 11:32 Michał Górny
2022-06-15 11:32 Michał Górny
2022-06-11 5:21 Arthur Zamarin
2022-06-04 7:00 Michał Górny
2022-05-25 7:12 Michał Górny
2022-05-16 13:24 Michał Górny
2022-05-12 7:13 Michał Górny
2022-05-11 8:05 Michał Górny
2022-05-10 10:07 Michał Górny
2022-04-21 20:48 Michał Górny
2022-04-15 7:16 Arthur Zamarin
2022-04-15 7:16 Arthur Zamarin
2022-04-13 5:30 Michał Górny
2022-04-13 5:30 Michał Górny
2022-03-09 20:33 Arthur Zamarin
2022-02-10 7:58 Michał Górny
2022-01-11 9:59 Michał Górny
2022-01-04 21:29 Arthur Zamarin
2021-12-18 8:48 Michał Górny
2021-02-22 22:20 Sam James
2021-02-22 22:20 Sam James
2020-10-15 1:44 Zac Medico
2020-03-28 17:44 Michał Górny
2020-01-26 21:41 Zac Medico
2020-01-26 21:21 Zac Medico
2018-06-24 16:40 Pacho Ramos
2017-11-07 19:03 Zac Medico
2017-11-07 3:00 Zac Medico
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=1614032384.0a14b4b22a0377e3bea5025245d52f2f8f519757.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