From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/apr-util/
Date: Thu, 28 Jul 2022 13:31:50 +0000 (UTC) [thread overview]
Message-ID: <1659015097.656f3ff1f820096e1b69e0830b0471c67735b9d6.sam@gentoo> (raw)
commit: 656f3ff1f820096e1b69e0830b0471c67735b9d6
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 28 13:26:34 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 28 13:31:37 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=656f3ff1
dev-libs/apr-util: add github upstream metadata
I know the README mentions it being dead but the other branches
are alive still.
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/apr-util/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dev-libs/apr-util/metadata.xml b/dev-libs/apr-util/metadata.xml
index 42bfa7fd8444..628ac167792d 100644
--- a/dev-libs/apr-util/metadata.xml
+++ b/dev-libs/apr-util/metadata.xml
@@ -9,4 +9,7 @@
<flag name="nss">Install apr_crypto_nss module</flag>
<flag name="openssl">Install apr_crypto_openssl module</flag>
</use>
+ <upstream>
+ <remote-id type="github">apache/apr-util</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2022-07-28 13:31 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 13:31 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 5:11 [gentoo-commits] repo/gentoo:master commit in: dev-libs/apr-util/ Eli Schwartz
2023-03-18 16:29 Hans de Graaff
2023-03-13 19:16 Arthur Zamarin
2023-02-16 5:22 Sam James
2023-02-14 23:05 Sam James
2023-02-14 21:43 Sam James
2023-02-14 21:43 Sam James
2023-02-14 21:43 Sam James
2023-02-14 7:05 Sam James
2023-02-14 6:37 Sam James
2023-01-26 5:20 Sam James
2022-12-18 14:00 James Le Cuirot
2022-12-17 19:33 Arthur Zamarin
2022-12-17 19:33 Arthur Zamarin
2022-12-14 11:45 Sam James
2022-12-11 0:26 Sam James
2022-11-26 17:12 Arthur Zamarin
2022-11-25 14:34 Arthur Zamarin
2022-11-18 7:07 Jakov Smolić
2022-11-16 7:05 Arthur Zamarin
2022-10-31 1:26 WANG Xuerui
2022-10-20 19:00 Jakov Smolić
2022-10-16 21:47 Sam James
2022-10-14 6:56 Agostino Sarubbo
2022-10-14 6:56 Agostino Sarubbo
2022-10-14 4:14 Arthur Zamarin
2022-10-13 23:01 Sam James
2022-10-13 23:01 Sam James
2022-10-13 22:37 Sam James
2022-07-03 9:51 Hans de Graaff
2022-05-14 0:47 Sam James
2022-03-23 0:45 Sam James
2021-07-28 11:28 Marek Szuba
2021-04-30 18:01 Mikle Kolyada
2020-01-01 11:50 Lars Wendler
2019-05-22 2:52 Aaron Bauman
2019-04-08 6:50 Sergei Trofimovich
2018-10-02 10:58 Tobias Klausmann
2018-09-24 18:17 Markus Meier
2018-09-19 17:35 Thomas Deutschmann
2018-09-16 19:52 Matt Turner
2018-09-16 19:52 Matt Turner
2018-09-15 12:10 Sergei Trofimovich
2018-09-14 18:48 Sergei Trofimovich
2018-09-14 9:20 Agostino Sarubbo
2018-09-13 13:47 Lars Wendler
2018-09-13 13:47 Lars Wendler
2018-08-17 1:38 Mikle Kolyada
2018-04-02 11:42 Pacho Ramos
2018-03-16 22:50 Lars Wendler
2018-01-04 10:31 Lars Wendler
2018-01-04 10:31 Lars Wendler
2017-10-23 8:55 Lars Wendler
2017-10-23 8:55 Lars Wendler
2017-06-18 8:59 Lars Wendler
2017-06-17 21:36 Lars Wendler
2017-06-01 7:42 Lars Wendler
2017-05-31 12:56 Lars Wendler
2017-05-31 6:56 Lars Wendler
2017-05-31 6:56 Lars Wendler
2017-03-22 11:10 Lars Wendler
2017-03-21 15:46 Michael Haubenwallner
2015-10-02 16:16 Julian Ospald
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=1659015097.656f3ff1f820096e1b69e0830b0471c67735b9d6.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