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/tilt/
Date: Sat, 23 Jul 2016 08:46:34 +0000 (UTC)	[thread overview]
Message-ID: <1469263591.3bbabd94d7eb481a39021fba6cf197899b1d5cb5.graaff@gentoo> (raw)

commit:     3bbabd94d7eb481a39021fba6cf197899b1d5cb5
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 23 08:28:07 2016 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Jul 23 08:46:31 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3bbabd94

dev-ruby/tilt: add ruby21 to stable version

Package-Manager: portage-2.2.28

 dev-ruby/tilt/tilt-1.4.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/tilt/tilt-1.4.1.ebuild b/dev-ruby/tilt/tilt-1.4.1.ebuild
index ec83010..aac0d31 100644
--- a/dev-ruby/tilt/tilt-1.4.1.ebuild
+++ b/dev-ruby/tilt/tilt-1.4.1.ebuild
@@ -5,7 +5,7 @@
 EAPI=5
 
 # jruby fails tests
-USE_RUBY="ruby20"
+USE_RUBY="ruby20 ruby21"
 
 RUBY_FAKEGEM_TASK_DOC=""
 RUBY_FAKEGEM_EXTRADOC="README.md TEMPLATES.md"


             reply	other threads:[~2016-07-23  8:46 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23  8:46 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-21  8:58 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/tilt/ Hans de Graaff
2024-11-03  7:27 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 12:01 Sam James
2024-10-06 11:52 Sam James
2024-10-06 11:52 Sam James
2024-06-28  4:31 Hans de Graaff
2023-12-29  7:40 Hans de Graaff
2023-09-15 10:09 Hans de Graaff
2023-09-15  5:52 Hans de Graaff
2023-08-20  8:47 Sam James
2023-08-19  6:10 Sam James
2023-08-19  6:09 Sam James
2023-07-09 18:25 Hans de Graaff
2023-04-23 22:17 Sam James
2023-04-23 20:03 Sam James
2023-04-23 20:00 Sam James
2023-04-23 19:56 Sam James
2023-04-23 19:52 Sam James
2023-04-23 19:50 Sam James
2023-03-24  3:58 Sam James
2023-03-22  3:25 Sam James
2023-01-21  8:44 Hans de Graaff
2022-12-04 18:07 Arthur Zamarin
2022-12-03 16:00 Arthur Zamarin
2022-12-03 11:48 Arthur Zamarin
2022-12-03  7:13 Hans de Graaff
2022-12-03  1:38 Sam James
2022-12-02 21:26 Sam James
2022-12-02 21:26 Sam James
2022-07-23  7:18 Hans de Graaff
2022-04-17  6:57 Hans de Graaff
2021-10-03  6:30 Hans de Graaff
2021-10-02 18:49 Sam James
2021-10-02 18:49 Sam James
2021-10-02 18:49 Sam James
2021-10-02 18:48 Sam James
2021-10-02 18:48 Sam James
2021-10-02 18:40 Sam James
2021-09-07 12:30 Marek Szuba
2021-01-06 18:32 Fabian Groffen
2020-04-26  8:58 Sergei Trofimovich
2020-02-17  6:04 Hans de Graaff
2020-01-13  6:09 Hans de Graaff
2019-10-04  6:02 Hans de Graaff
2019-05-13  5:31 Hans de Graaff
2019-05-13  1:41 Thomas Deutschmann
2019-04-28 20:18 Mikle Kolyada
2019-04-27 16:25 Sergei Trofimovich
2019-04-27 16:03 Sergei Trofimovich
2019-04-23 19:30 Mikle Kolyada
2019-04-10  6:24 Hans de Graaff
2019-01-16  7:24 Hans de Graaff
2018-12-14  7:43 Hans de Graaff
2018-07-04 20:56 Hans de Graaff
2018-04-27  5:42 Hans de Graaff
2018-02-24  8:50 Hans de Graaff
2017-10-01  0:56 Thomas Deutschmann
2017-07-27  7:13 Hans de Graaff
2017-07-12  4:48 Hans de Graaff
2017-06-30 11:17 Alexis Ballier
2017-06-23  4:52 Hans de Graaff
2017-06-23  3:38 Hans de Graaff
2017-06-02  5:38 Hans de Graaff
2017-02-27 18:55 Michael Weber
2017-02-27 17:01 Michael Weber
2016-12-11 19:17 Hans de Graaff
2016-12-11 19:17 Hans de Graaff
2016-12-11 19:17 Hans de Graaff
2016-08-16 12:43 Manuel Rüger
2016-07-22  7:05 Hans de Graaff
2016-06-04  3:50 Hans de Graaff
2016-05-19  5:30 Hans de Graaff
2016-05-13  5:18 Hans de Graaff
2016-03-06 19:21 Manuel Rüger
2016-01-08  6:45 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=1469263591.3bbabd94d7eb481a39021fba6cf197899b1d5cb5.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