From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/ant-core/
Date: Mon, 11 Dec 2023 19:21:59 +0000 (UTC) [thread overview]
Message-ID: <1702322515.f08ffdc068486820c01506309d941b9c3d172964.fordfrog@gentoo> (raw)
commit: f08ffdc068486820c01506309d941b9c3d172964
Author: Volkmar W. Pogatzki <gentoo <AT> pogatzki <DOT> net>
AuthorDate: Mon Dec 11 09:05:11 2023 +0000
Commit: Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Mon Dec 11 19:21:55 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f08ffdc0
dev-java/ant-core: add github upstream metadata
Signed-off-by: Volkmar W. Pogatzki <gentoo <AT> pogatzki.net>
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>
dev-java/ant-core/metadata.xml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/dev-java/ant-core/metadata.xml b/dev-java/ant-core/metadata.xml
index 4221e170cbc0..d0bcffb03628 100644
--- a/dev-java/ant-core/metadata.xml
+++ b/dev-java/ant-core/metadata.xml
@@ -5,4 +5,9 @@
<email>java@gentoo.org</email>
<name>Java</name>
</maintainer>
+ <upstream>
+ <bugs-to>https://bz.apache.org/bugzilla/enter_bug.cgi?product=Ant</bugs-to>
+ <doc>https://ant.apache.org/manual/</doc>
+ <remote-id type="github">apache/ant</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2023-12-11 19:22 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 19:21 Miroslav Šulc [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-27 17:39 [gentoo-commits] repo/gentoo:master commit in: dev-java/ant-core/ Eli Schwartz
2024-03-10 21:10 Miroslav Šulc
2024-03-10 21:10 Miroslav Šulc
2024-03-10 8:53 Arthur Zamarin
2024-03-03 6:11 Sam James
2024-02-25 23:06 Sam James
2024-02-25 19:19 Jakov Smolić
2024-01-26 2:09 Ionen Wolkens
2024-01-26 2:09 Ionen Wolkens
2024-01-23 9:42 Miroslav Šulc
2022-05-21 18:19 Florian Schmaus
2022-05-20 8:45 Florian Schmaus
2022-05-12 18:23 Florian Schmaus
2022-03-22 17:47 Arthur Zamarin
2022-03-22 11:26 Agostino Sarubbo
2022-03-22 9:27 Jakov Smolić
2022-03-22 9:27 Jakov Smolić
2022-03-22 8:37 Arthur Zamarin
2022-02-19 9:25 Miroslav Šulc
2022-02-19 9:25 Miroslav Šulc
2022-02-03 6:56 Florian Schmaus
2022-01-30 9:00 Florian Schmaus
2022-01-30 9:00 Florian Schmaus
2022-01-18 9:51 Miroslav Šulc
2020-12-27 14:07 Fabian Groffen
2020-10-15 7:42 Miroslav Šulc
2020-10-14 19:22 Agostino Sarubbo
2020-10-14 19:19 Agostino Sarubbo
2020-10-14 19:08 Agostino Sarubbo
2020-10-14 18:29 Sam James
2020-10-01 18:16 Miroslav Šulc
2020-07-19 21:35 Sam James
2020-07-19 15:18 Sam James
2020-07-19 13:38 Sam James
2020-07-05 11:20 Miroslav Šulc
2019-11-25 13:22 Miroslav Šulc
2019-11-25 13:22 Miroslav Šulc
2019-11-23 16:49 Agostino Sarubbo
2019-11-23 12:43 Agostino Sarubbo
2019-11-23 5:42 Aaron Bauman
2019-11-22 10:24 Agostino Sarubbo
2019-11-01 10:31 Miroslav Šulc
2019-10-17 14:02 Miroslav Šulc
2019-04-30 8:40 Michał Górny
2019-03-20 17:27 Miroslav Šulc
2019-03-15 8:21 Mikle Kolyada
2019-03-01 12:46 Mikle Kolyada
2019-03-01 1:14 Thomas Deutschmann
2019-01-24 22:06 Miroslav Šulc
2019-01-23 8:28 Miroslav Šulc
2019-01-21 10:29 Miroslav Šulc
2018-02-12 22:18 James Le Cuirot
2017-01-30 19:03 Fabian Groffen
2017-01-27 9:34 Patrick Lauer
2017-01-26 21:50 James Le Cuirot
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=1702322515.f08ffdc068486820c01506309d941b9c3d172964.fordfrog@gentoo \
--to=fordfrog@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