From: "Anna Vyalkova" <cyber+gentoo@sysrq.in>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/sphinx-click/
Date: Wed, 5 Jul 2023 13:59:27 +0000 (UTC) [thread overview]
Message-ID: <1688565456.41f9407f354e2fcae068cae229052dca02c33135.cybertailor@gentoo> (raw)
commit: 41f9407f354e2fcae068cae229052dca02c33135
Author: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Wed Jul 5 13:35:31 2023 +0000
Commit: Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
CommitDate: Wed Jul 5 13:57:36 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=41f9407f
dev-python/sphinx-click: update upstream metadata
Signed-off-by: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq.in>
dev-python/sphinx-click/metadata.xml | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/dev-python/sphinx-click/metadata.xml b/dev-python/sphinx-click/metadata.xml
index e1c7001b5..a68e36a02 100644
--- a/dev-python/sphinx-click/metadata.xml
+++ b/dev-python/sphinx-click/metadata.xml
@@ -1,15 +1,17 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>lssndrbarbieri@gmail.com</email>
- <name>Alessandro Barbieri</name>
- </maintainer>
- <longdescription lang="en">
+ <maintainer type="person">
+ <email>lssndrbarbieri@gmail.com</email>
+ <name>Alessandro Barbieri</name>
+ </maintainer>
+ <longdescription lang="en">
sphinx-click is a Sphinx plugin that allows you to automatically extract documentation from a click-based application and include it in your docs.
</longdescription>
- <upstream>
- <remote-id type="github">click-contrib/sphinx-click</remote-id>
- <remote-id type="pypi">sphinx-click</remote-id>
- </upstream>
+ <upstream>
+ <remote-id type="github">click-contrib/sphinx-click</remote-id>
+ <remote-id type="pypi">sphinx-click</remote-id>
+ <bugs-to>https://github.com/click-contrib/sphinx-click/issues</bugs-to>
+ <doc>https://sphinx-click.readthedocs.io/en/latest</doc>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2023-07-05 13:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 13:59 Anna Vyalkova [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-14 20:12 [gentoo-commits] repo/proj/guru:master commit in: dev-python/sphinx-click/ Julien Roy
2024-05-14 20:07 ` [gentoo-commits] repo/proj/guru:dev " Julien Roy
2024-05-14 20:12 [gentoo-commits] repo/proj/guru:master " Julien Roy
2024-05-14 20:07 ` [gentoo-commits] repo/proj/guru:dev " Julien Roy
2024-05-14 20:07 Julien Roy
2023-03-17 13:32 Anna Vyalkova
2022-06-28 4:34 Alessandro Barbieri
2022-06-14 8:00 Alessandro Barbieri
2022-06-14 8:00 Alessandro Barbieri
2022-04-20 22:37 Alessandro Barbieri
2022-04-16 0:29 Alessandro Barbieri
2022-03-14 2:41 Alessandro Barbieri
2021-12-15 10:35 Andrew Ammerlaan
2021-12-14 7:14 Anna Vyalkova
2021-06-15 23:28 Alessandro Barbieri
2021-06-14 23:09 Alessandro Barbieri
2021-06-14 2:27 Alessandro Barbieri
2021-05-07 11:31 Alessandro Barbieri
2021-05-07 0:41 Anna Vyalkova
2021-05-06 23:07 Alessandro Barbieri
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=1688565456.41f9407f354e2fcae068cae229052dca02c33135.cybertailor@gentoo \
--to=cyber+gentoo@sysrq.in \
--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