From: "Sergey Torokhov" <torokhov-s-a@yandex.ru>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/markdown-include/
Date: Mon, 6 Sep 2021 19:50:07 +0000 (UTC) [thread overview]
Message-ID: <1630957446.c5d747e83f1d6a727f814f4116ec40837fe49d87.SergeyTorokhov@gentoo> (raw)
commit: c5d747e83f1d6a727f814f4116ec40837fe49d87
Author: Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
AuthorDate: Mon Sep 6 19:44:06 2021 +0000
Commit: Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
CommitDate: Mon Sep 6 19:44:06 2021 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=c5d747e8
dev-python/markdown-include: add maintainer, longdescription; rm py3.7
Signed-off-by: Sergey Torokhov <torokhov-s-a <AT> yandex.ru>
dev-python/markdown-include/markdown-include-0.6.0.ebuild | 4 ++--
dev-python/markdown-include/metadata.xml | 10 ++++++++--
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/dev-python/markdown-include/markdown-include-0.6.0.ebuild b/dev-python/markdown-include/markdown-include-0.6.0.ebuild
index a26f96419..2d24ec8b2 100644
--- a/dev-python/markdown-include/markdown-include-0.6.0.ebuild
+++ b/dev-python/markdown-include/markdown-include-0.6.0.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
-PYTHON_COMPAT=( python3_{7,8,9} )
+PYTHON_COMPAT=( python3_{8..9} )
inherit distutils-r1
diff --git a/dev-python/markdown-include/metadata.xml b/dev-python/markdown-include/metadata.xml
index a91e226f4..34949af60 100644
--- a/dev-python/markdown-include/metadata.xml
+++ b/dev-python/markdown-include/metadata.xml
@@ -1,8 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-
<pkgmetadata>
- <!-- maintainer-needed -->
+ <maintainer type="person">
+ <email>torokhov-s-a@yandex.ru</email>
+ <name>Sergey Torokhov</name>
+ </maintainer>
+ <longdescription lang="en">
+ An extension to Python-Markdown which provides an "include" function,
+ similar to that found in LaTeX (and also the C pre-processor and Fortran).
+ </longdescription>
<upstream>
<remote-id type="github">cmacmackin/markdown-include</remote-id>
<remote-id type="pypi">markdown-include</remote-id>
next reply other threads:[~2021-09-06 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 19:50 Sergey Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-09 2:00 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/markdown-include/ Anna Vyalkova
2023-03-18 12:07 Sergey Torokhov
2023-03-17 13:10 Anna Vyalkova
2023-02-26 22:31 Sergey Torokhov
2023-01-19 0:11 Sergey Torokhov
2022-12-09 17:46 Sergey Torokhov
2022-12-09 17:41 Sergey Torokhov
2022-12-03 16:22 Sergey Torokhov
2022-10-28 21:46 Sergey Torokhov
2022-08-02 22:11 Sergey Torokhov
2022-02-23 12:13 Sergey Torokhov
2021-05-24 11:06 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-05-24 10:01 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-11-20 16:03 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-11-20 16:03 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-04-28 17:30 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=1630957446.c5d747e83f1d6a727f814f4116ec40837fe49d87.SergeyTorokhov@gentoo \
--to=torokhov-s-a@yandex.ru \
--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