From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/patron/
Date: Mon, 3 Apr 2023 00:47:52 +0000 (UTC) [thread overview]
Message-ID: <1680482795.ffb8c49d09df5b2460bf9be00d4ba50ba31982e8.sam@gentoo> (raw)
commit: ffb8c49d09df5b2460bf9be00d4ba50ba31982e8
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 3 00:45:07 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 3 00:46:35 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ffb8c49d
dev-ruby/patron: add github upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/patron/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dev-ruby/patron/metadata.xml b/dev-ruby/patron/metadata.xml
index 658c72b1920d..3381fedd792f 100644
--- a/dev-ruby/patron/metadata.xml
+++ b/dev-ruby/patron/metadata.xml
@@ -5,4 +5,7 @@
<email>ruby@gentoo.org</email>
<name>Gentoo Ruby Project</name>
</maintainer>
+<upstream>
+ <remote-id type="github">toland/patron</remote-id>
+</upstream>
</pkgmetadata>
next reply other threads:[~2023-04-03 0:48 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 0:47 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-28 14:21 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/patron/ Hans de Graaff
2025-02-28 14:21 Hans de Graaff
2024-10-06 11:36 Sam James
2024-10-06 11:11 Sam James
2024-02-29 7:14 Hans de Graaff
2023-09-15 14:56 Hans de Graaff
2023-07-12 6:39 Jakov Smolić
2023-07-11 14:02 Jakov Smolić
2023-07-11 7:47 Hans de Graaff
2023-04-09 3:33 Sam James
2023-04-07 15:03 Sam James
2023-04-07 15:03 Sam James
2023-04-07 15:03 Sam James
2023-04-07 15:03 Sam James
2023-04-07 15:03 Sam James
2023-04-03 0:47 Sam James
2023-02-04 7:08 Hans de Graaff
2022-12-24 6:35 Sam James
2021-10-23 7:05 Hans de Graaff
2021-10-20 6:56 Agostino Sarubbo
2021-10-17 20:04 Sam James
2021-10-17 6:04 Hans de Graaff
2021-07-16 8:52 Hans de Graaff
2021-07-12 13:26 Hans de Graaff
2020-05-30 18:36 Hans de Graaff
2020-05-30 18:36 Hans de Graaff
2019-05-23 5:39 Hans de Graaff
2019-04-29 18:34 Hans de Graaff
2019-04-29 5:32 Hans de Graaff
2019-04-28 20:34 Thomas Deutschmann
2019-04-13 14:10 Mikle Kolyada
2018-12-26 11:48 Sergei Trofimovich
2018-12-22 6:44 Hans de Graaff
2018-12-19 6:22 Hans de Graaff
2018-12-19 6:22 Hans de Graaff
2018-05-01 4:45 Hans de Graaff
2018-04-30 20:11 Hans de Graaff
2018-03-22 20:23 Jeroen Roovers
2018-03-02 6:39 Hans de Graaff
2018-02-08 6:25 Hans de Graaff
2018-01-31 6:03 Hans de Graaff
2018-01-22 19:26 Hans de Graaff
2018-01-21 21:17 Thomas Deutschmann
2018-01-21 6:43 Hans de Graaff
2018-01-20 10:19 Hans de Graaff
2017-10-05 4:50 Hans de Graaff
2017-08-26 8:27 Hans de Graaff
2017-07-19 6:55 Hans de Graaff
2017-07-19 6:55 Hans de Graaff
2017-05-08 5:27 Hans de Graaff
2017-05-08 5:27 Hans de Graaff
2016-09-07 4:48 Hans de Graaff
2016-09-02 6:14 Hans de Graaff
2016-09-02 6:14 Hans de Graaff
2016-06-14 4:51 Hans de Graaff
2016-06-03 5:19 Hans de Graaff
2016-05-30 5:35 Hans de Graaff
2016-05-05 5:27 Hans de Graaff
2016-04-11 5:12 Hans de Graaff
2016-04-11 5:12 Hans de Graaff
2016-04-11 5:12 Hans de Graaff
2016-03-15 5:53 Hans de Graaff
2016-01-03 5:38 Richard Farina
2015-09-08 5:35 Hans de Graaff
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=1680482795.ffb8c49d09df5b2460bf9be00d4ba50ba31982e8.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