From: "Rick Farina" <zerochaos@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/blinkstick/
Date: Mon, 4 Mar 2024 18:33:45 +0000 (UTC) [thread overview]
Message-ID: <1709577193.3258f04fc4db4572cb51433e9ef8f231aa7f4c94.zerochaos@gentoo> (raw)
commit: 3258f04fc4db4572cb51433e9ef8f231aa7f4c94
Author: Rick Farina <zerochaos <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 4 16:57:58 2024 +0000
Commit: Rick Farina <zerochaos <AT> gentoo <DOT> org>
CommitDate: Mon Mar 4 18:33:13 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3258f04f
dev-ruby/blinkstick: update maintainers
Per discussion with Graaff, dropping myself as maintainer for everything
I originally added as a metasploit deps or worked on because it was a
metasploit dep. Adding ruby project where missing
Signed-off-by: Rick Farina <zerochaos <AT> gentoo.org>
dev-ruby/blinkstick/metadata.xml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/dev-ruby/blinkstick/metadata.xml b/dev-ruby/blinkstick/metadata.xml
index 394f1d579ac4..62ef42604c64 100644
--- a/dev-ruby/blinkstick/metadata.xml
+++ b/dev-ruby/blinkstick/metadata.xml
@@ -5,6 +5,10 @@
<email>zerochaos@gentoo.org</email>
<name>Rick Farina</name>
</maintainer>
+ <maintainer type="project">
+ <email>ruby@gentoo.org</email>
+ <name>Gentoo Ruby Project</name>
+ </maintainer>
<upstream>
<remote-id type="github">arvydas/blinkstick-ruby</remote-id>
</upstream>
next reply other threads:[~2024-03-04 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 18:33 Rick Farina [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 5:25 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/blinkstick/ Hans de Graaff
2023-03-12 12:09 Hans de Graaff
2022-07-20 6:01 Hans de Graaff
2022-06-18 8:40 Hans de Graaff
2019-04-19 5:46 Hans de Graaff
2019-04-18 20:40 Rick Farina
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=1709577193.3258f04fc4db4572cb51433e9ef8f231aa7f4c94.zerochaos@gentoo \
--to=zerochaos@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