From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pelican-minify/
Date: Tue, 21 Feb 2023 16:46:35 +0000 (UTC) [thread overview]
Message-ID: <1676997930.dcedd8f65c70919d7b9261e466454e39a6929b04.sam@gentoo> (raw)
commit: dcedd8f65c70919d7b9261e466454e39a6929b04
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 21 16:38:54 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Feb 21 16:45:30 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dcedd8f6
dev-python/pelican-minify: add github upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pelican-minify/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/pelican-minify/metadata.xml b/dev-python/pelican-minify/metadata.xml
index 90e73ab55bc1..dd1f5ee146c6 100644
--- a/dev-python/pelican-minify/metadata.xml
+++ b/dev-python/pelican-minify/metadata.xml
@@ -11,6 +11,7 @@
</maintainer>
<stabilize-allarches/>
<upstream>
+ <remote-id type="github">rdegges/pelican-minify</remote-id>
<remote-id type="pypi">pelican-minify</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2023-02-21 16:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 16:46 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-17 14:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/pelican-minify/ Michał Górny
2023-12-28 4:56 Sam James
2023-12-15 9:06 Michał Górny
2023-10-20 13:33 Michał Górny
2023-08-04 3:03 Michał Górny
2023-02-28 20:27 Michał Górny
2023-02-21 16:46 Sam James
2023-02-21 16:46 Sam James
2022-05-20 1:59 Matthew Thode
2021-02-22 22:20 Sam James
2021-02-22 22:20 Sam James
2020-01-29 2:58 Matthew Thode
2018-06-24 16:21 Pacho Ramos
2017-10-21 18:43 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=1676997930.dcedd8f65c70919d7b9261e466454e39a6929b04.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