From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/collective-checkdocs/
Date: Sat, 14 Nov 2020 21:52:40 +0000 (UTC) [thread overview]
Message-ID: <1605390754.321bf8c466a5f75ccd78795aa26804a71a40ea6e.mgorny@gentoo> (raw)
commit: 321bf8c466a5f75ccd78795aa26804a71a40ea6e
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 14 21:30:26 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sat Nov 14 21:52:34 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=321bf8c4
dev-python/collective-checkdocs: Mark ALLARCHES
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/collective-checkdocs/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/collective-checkdocs/metadata.xml b/dev-python/collective-checkdocs/metadata.xml
index b3409eaec2a..bba9c09c9ae 100644
--- a/dev-python/collective-checkdocs/metadata.xml
+++ b/dev-python/collective-checkdocs/metadata.xml
@@ -11,6 +11,7 @@
<longdescription lang="en">
collective.checkdocs adds new distutils commands checkdocs and showdocs to validate restructured text in long_description field of Python eggs. This package aims to make Python egg help page publishing and editing easier.
</longdescription>
+ <stabilize-allarches/>
<upstream>
<remote-id type="pypi">collective.checkdocs</remote-id>
<remote-id type="github">collective/collective.checkdocs</remote-id>
next reply other threads:[~2020-11-14 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 21:52 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-09 17:29 [gentoo-commits] repo/gentoo:master commit in: dev-python/collective-checkdocs/ Arthur Zamarin
2020-11-15 7:54 Michał Górny
2020-11-15 5:19 Sam James
2020-10-01 21:56 Louis Sautier
2020-10-01 21:56 Louis Sautier
2020-03-19 18:44 Michał Górny
2019-04-10 22:44 Matthew Thode
2017-12-12 20:24 Matt Thode
2017-11-13 3:12 Matt Thode
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=1605390754.321bf8c466a5f75ccd78795aa26804a71a40ea6e.mgorny@gentoo \
--to=mgorny@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