From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/eventmachine/
Date: Sun, 12 Mar 2023 12:09:38 +0000 (UTC) [thread overview]
Message-ID: <1678622972.14519433f24d00d8543afa4c7e04ca4392e2ea1d.graaff@gentoo> (raw)
commit: 14519433f24d00d8543afa4c7e04ca4392e2ea1d
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 12 08:24:10 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Mar 12 12:09:32 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=14519433
dev-ruby/eventmachine: add github, rubygems upstream metadata
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/eventmachine/metadata.xml | 21 ++++++++++++++-------
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/dev-ruby/eventmachine/metadata.xml b/dev-ruby/eventmachine/metadata.xml
index 9a6d487f6b15..21498041991b 100644
--- a/dev-ruby/eventmachine/metadata.xml
+++ b/dev-ruby/eventmachine/metadata.xml
@@ -1,11 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
-<maintainer type="project">
- <email>ruby@gentoo.org</email>
- <name>Gentoo Ruby Project</name>
-</maintainer>
-<longdescription>
-Ruby/EventMachine is a fast, simple event-processing library for Ruby programs. It lets you write network clients and servers without handling sockets- all you do is send and receive data. Single-threaded socket engine- scalable and FAST!
-</longdescription>
+ <maintainer type="project">
+ <email>ruby@gentoo.org</email>
+ <name>Gentoo Ruby Project</name>
+ </maintainer>
+ <upstream>
+ <remote-id type="github">eventmachine/eventmachine</remote-id>
+ <remote-id type="rubygems">eventmachine</remote-id>
+ </upstream>
+ <longdescription>
+ Ruby/EventMachine is a fast, simple event-processing library for
+ Ruby programs. It lets you write network clients and servers without
+ handling sockets- all you do is send and receive
+ data. Single-threaded socket engine- scalable and FAST!
+ </longdescription>
</pkgmetadata>
next reply other threads:[~2023-03-12 12:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 12:09 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-29 13:04 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/eventmachine/ Sam James
2023-03-29 11:48 Sam James
2023-03-29 11:38 Sam James
2022-07-30 7:46 Hans de Graaff
2022-06-26 6:44 Hans de Graaff
2022-06-18 20:25 Sam James
2022-06-18 20:25 Sam James
2021-09-28 19:34 Sam James
2021-09-28 1:09 Sam James
2021-09-28 1:08 Sam James
2021-09-28 1:01 Sam James
2021-06-22 18:19 Sam James
2020-05-23 6:34 Hans de Graaff
2019-02-02 10:36 Hans de Graaff
2018-07-15 19:05 Hans de Graaff
2018-07-15 19:05 Hans de Graaff
2018-05-18 5:56 Hans de Graaff
2018-04-26 4:57 Hans de Graaff
2018-04-17 18:29 Hans de Graaff
2018-04-16 18:32 Hans de Graaff
2018-02-25 7:47 Hans de Graaff
2018-02-25 6:47 Hans de Graaff
2016-06-26 5:38 Hans de Graaff
2016-03-17 11:56 Agostino Sarubbo
2016-03-17 6:39 Hans de Graaff
2016-03-17 6:39 Hans de Graaff
2016-03-17 6:39 Hans de Graaff
2016-01-14 20:37 Manuel Rüger
2016-01-14 20:37 Manuel Rüger
2015-10-03 9:12 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=1678622972.14519433f24d00d8543afa4c7e04ca4392e2ea1d.graaff@gentoo \
--to=graaff@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