public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/crack/
Date: Wed,  1 May 2019 19:36:39 +0000 (UTC)	[thread overview]
Message-ID: <1556739384.fdd72f6431b37e67ee2c4054bf52f8d170e1e8e0.graaff@gentoo> (raw)

commit:     fdd72f6431b37e67ee2c4054bf52f8d170e1e8e0
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed May  1 19:03:53 2019 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed May  1 19:36:24 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fdd72f64

dev-ruby/crack: add ruby26

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11

 dev-ruby/crack/crack-0.4.3-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/crack/crack-0.4.3-r2.ebuild b/dev-ruby/crack/crack-0.4.3-r2.ebuild
index 65d88c010de..f1842a72292 100644
--- a/dev-ruby/crack/crack-0.4.3-r2.ebuild
+++ b/dev-ruby/crack/crack-0.4.3-r2.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=6
 
-USE_RUBY="ruby23 ruby24 ruby25"
+USE_RUBY="ruby23 ruby24 ruby25 ruby26"
 
 RUBY_FAKEGEM_RECIPE_DOC="rdoc"
 RUBY_FAKEGEM_EXTRADOC="README.md History"


             reply	other threads:[~2019-05-01 19:36 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 19:36 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-30 10:18 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/crack/ Hans de Graaff
2024-10-15  1:03 Sam James
2024-10-12  8:23 Hans de Graaff
2024-10-10 11:04 Arthur Zamarin
2024-10-09  5:46 Sam James
2024-10-06 18:39 Arthur Zamarin
2024-10-06 13:30 Arthur Zamarin
2024-10-06 11:35 Sam James
2024-09-11 15:04 Arthur Zamarin
2024-07-12  6:21 Ionen Wolkens
2024-07-02  3:56 Ionen Wolkens
2024-06-08 11:12 Arthur Zamarin
2024-03-17  6:01 Hans de Graaff
2024-02-13 10:32 Hans de Graaff
2023-12-27 20:33 Hans de Graaff
2023-12-05 18:25 Ionen Wolkens
2023-03-28 18:51 Sam James
2023-03-28 16:07 Sam James
2023-03-28 16:04 Sam James
2023-03-28 16:00 Sam James
2023-03-28 16:00 Sam James
2023-03-28 16:00 Sam James
2023-03-18  0:02 Sam James
2022-08-02  5:35 Hans de Graaff
2022-07-24  7:26 Hans de Graaff
2022-06-28 16:59 Arthur Zamarin
2022-06-28 16:47 Arthur Zamarin
2022-04-27  4:34 Arthur Zamarin
2022-04-26 13:45 Sam James
2022-04-01  5:15 Arthur Zamarin
2021-10-17  8:33 Hans de Graaff
2021-09-19 21:39 Agostino Sarubbo
2021-09-19 21:35 Agostino Sarubbo
2021-08-11 14:29 Marek Szuba
2021-06-22  5:21 Hans de Graaff
2020-09-18  5:34 Hans de Graaff
2020-04-19 12:22 Sergei Trofimovich
2019-04-29  5:32 Hans de Graaff
2019-04-28 20:34 Thomas Deutschmann
2019-04-13 14:10 Mikle Kolyada
2018-06-01 17:11 Hans de Graaff
2018-01-22 20:25 Hans de Graaff
2018-01-21 21:17 Thomas Deutschmann
2018-01-21  6:43 Hans de Graaff
2017-08-27  6:18 Hans de Graaff
2017-07-12  4:48 Hans de Graaff
2017-07-12  4:48 Hans de Graaff
2016-10-13  5:25 Hans de Graaff
2016-07-22 19:04 Hans de Graaff
2016-07-22 19:04 Hans de Graaff
2016-06-13  4:37 Richard Farina
2016-04-25 23:20 Manuel Rüger
2015-12-04  6:50 Hans de Graaff
2015-10-23  9:26 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=1556739384.fdd72f6431b37e67ee2c4054bf52f8d170e1e8e0.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