From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/miniupnpd/
Date: Mon, 16 May 2022 23:06:10 +0000 (UTC) [thread overview]
Message-ID: <1652742345.4d2516123d670c287f4d63b5e5c002a60bb0ab63.sam@gentoo> (raw)
commit: 4d2516123d670c287f4d63b5e5c002a60bb0ab63
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon May 16 23:05:45 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon May 16 23:05:45 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d251612
net-misc/miniupnpd: add github upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-misc/miniupnpd/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net-misc/miniupnpd/metadata.xml b/net-misc/miniupnpd/metadata.xml
index 37183016068f..e1c5b875f102 100644
--- a/net-misc/miniupnpd/metadata.xml
+++ b/net-misc/miniupnpd/metadata.xml
@@ -17,4 +17,7 @@
<flag name="portinuse">Check if a port is in use before allowing a NAT-PMP client to map it.</flag>
<flag name="strict">Be more strict regarding compliance with UPnP specifications.</flag>
</use>
+ <upstream>
+ <remote-id type="github">miniupnp/miniupnp</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2022-05-16 23:06 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 23:06 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-23 2:53 [gentoo-commits] repo/gentoo:master commit in: net-misc/miniupnpd/ Michał Górny
2024-03-20 6:28 Michał Górny
2024-03-20 6:28 Michał Górny
2024-03-02 19:47 Michał Górny
2024-01-04 4:35 Michał Górny
2024-01-04 4:35 Michał Górny
2023-01-20 4:50 Michał Górny
2022-10-22 6:22 Michał Górny
2022-10-22 6:22 Michał Górny
2022-10-18 7:26 Michał Górny
2022-07-18 0:26 Sam James
2022-02-18 2:44 Sam James
2022-01-23 9:33 Michał Górny
2021-12-23 8:14 Sam James
2021-08-22 8:01 Michał Górny
2021-05-14 8:14 Michał Górny
2020-12-21 9:29 Michał Górny
2020-12-21 9:29 Michał Górny
2020-11-01 7:20 Michał Górny
2020-10-31 8:33 Michał Górny
2020-10-10 18:21 Michał Górny
2020-09-29 2:14 Michał Górny
2020-09-18 9:38 Michał Górny
2020-05-14 6:26 Michał Górny
2020-05-04 9:37 Michał Górny
2020-04-02 7:32 Michał Górny
2020-04-02 7:32 Michał Górny
2019-12-29 20:51 Michał Górny
2019-10-07 8:05 Michał Górny
2019-09-25 5:53 Michał Górny
2019-09-08 6:43 Michał Górny
2019-09-02 2:53 Michał Górny
2019-08-28 5:36 Michał Górny
2019-07-01 7:56 Michał Górny
2019-06-26 15:47 Michał Górny
2019-05-24 21:55 Michał Górny
2019-05-03 7:15 Michał Górny
2019-04-10 15:07 Michał Górny
2019-04-08 19:17 Michał Górny
2019-04-05 5:23 Michał Górny
2019-03-10 8:08 Michał Górny
2019-02-13 14:28 Michał Górny
2019-02-13 14:28 Michał Górny
2018-09-06 21:22 Michał Górny
2018-07-07 5:31 Michał Górny
2018-07-07 5:31 Michał Górny
2018-05-05 15:27 Michał Górny
2018-05-05 15:27 Michał Górny
2018-04-23 13:44 Michał Górny
2018-04-11 7:03 Michał Górny
2018-03-13 11:59 Pacho Ramos
2018-02-25 20:04 Michał Górny
2018-02-04 8:44 Michał Górny
2018-01-02 6:19 Michał Górny
2017-12-13 7:56 Michał Górny
2017-12-13 7:56 Michał Górny
2017-11-26 23:23 David Seifert
2017-01-26 20:14 Michał Górny
2016-05-24 7:58 Michał Górny
2016-04-20 18:52 Patrick McLean
2016-04-13 1:12 Patrick McLean
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=1652742345.4d2516123d670c287f4d63b5e5c002a60bb0ab63.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