From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/octokit/
Date: Wed, 17 Feb 2021 05:59:16 +0000 (UTC) [thread overview]
Message-ID: <1613541552.9ff5545a01f9e3d8fb3e4179e490e71d1520f95d.graaff@gentoo> (raw)
commit: 9ff5545a01f9e3d8fb3e4179e490e71d1520f95d
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 17 05:59:12 2021 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Feb 17 05:59:12 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9ff5545a
dev-ruby/octokit: add ruby27
Package-Manager: Portage-3.0.13, Repoman-3.0.2
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/octokit/octokit-4.20.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/octokit/octokit-4.20.0.ebuild b/dev-ruby/octokit/octokit-4.20.0.ebuild
index fcc88dfcc4e..85e02ff81cf 100644
--- a/dev-ruby/octokit/octokit-4.20.0.ebuild
+++ b/dev-ruby/octokit/octokit-4.20.0.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=7
-USE_RUBY="ruby25 ruby26"
+USE_RUBY="ruby25 ruby26 ruby27"
RUBY_FAKEGEM_RECIPE_DOC="yard"
RUBY_FAKEGEM_RECIPE_TEST="rspec3"
next reply other threads:[~2021-02-17 5:59 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 5:59 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-23 10:31 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/octokit/ Hans de Graaff
2024-06-16 5:49 Hans de Graaff
2024-06-16 5:49 Hans de Graaff
2024-03-10 15:19 Hans de Graaff
2024-01-01 10:47 Hans de Graaff
2024-01-01 10:47 Hans de Graaff
2023-09-30 7:20 Hans de Graaff
2023-09-01 16:30 Arthur Zamarin
2023-09-01 3:56 Sam James
2023-08-31 19:14 Hans de Graaff
2023-08-29 16:53 Hans de Graaff
2023-08-26 7:20 Hans de Graaff
2023-06-17 5:09 Hans de Graaff
2023-04-17 6:01 Hans de Graaff
2023-03-30 7:01 Hans de Graaff
2023-03-27 10:03 Hans de Graaff
2022-07-13 9:25 Hans de Graaff
2022-07-06 5:28 Hans de Graaff
2022-06-18 5:48 Hans de Graaff
2022-06-07 18:31 Hans de Graaff
2022-05-28 5:39 Hans de Graaff
2022-05-08 7:28 Hans de Graaff
2022-05-01 6:34 Hans de Graaff
2022-01-14 7:29 Hans de Graaff
2021-07-07 8:31 Hans de Graaff
2021-04-30 5:52 Hans de Graaff
2021-01-03 8:05 Hans de Graaff
2020-10-24 9:00 Hans de Graaff
2020-10-23 4:49 Hans de Graaff
2020-09-11 5:14 Hans de Graaff
2020-07-17 0:54 Sam James
2020-06-26 12:42 Hans de Graaff
2020-05-24 7:09 Hans de Graaff
2020-05-24 7:09 Hans de Graaff
2020-03-29 7:43 Hans de Graaff
2020-03-11 7:16 Hans de Graaff
2020-02-06 7:00 Hans de Graaff
2020-01-03 6:53 Hans de Graaff
2019-07-17 8:00 Hans de Graaff
2019-05-05 7:28 Hans de Graaff
2019-05-02 6:36 Hans de Graaff
2019-03-31 8:00 Hans de Graaff
2018-11-21 18:21 Rick Farina
2018-11-11 10:54 Hans de Graaff
2018-11-11 10:54 Hans de Graaff
2017-09-24 7:10 Hans de Graaff
2017-05-09 3:09 Richard Farina
2016-12-23 23:46 Manuel Rüger
2016-12-23 23:46 Manuel Rüger
2016-12-16 6:15 Hans de Graaff
2016-11-20 18:42 Manuel Rüger
2016-11-08 21:58 Manuel Rüger
2016-10-28 19:42 Manuel Rüger
2016-07-01 16:59 Richard Farina
2016-06-13 4:37 Richard Farina
2016-06-10 19:19 Richard Farina
2016-03-05 6:54 Hans de Graaff
2016-02-21 11:03 Manuel Rüger
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=1613541552.9ff5545a01f9e3d8fb3e4179e490e71d1520f95d.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