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/css_parser/
Date: Mon, 26 Jun 2017 04:14:25 +0000 (UTC)	[thread overview]
Message-ID: <1498450451.ff1b80c5b2468dc63a940691b495145e07876bbf.graaff@gentoo> (raw)

commit:     ff1b80c5b2468dc63a940691b495145e07876bbf
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 26 04:14:11 2017 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Jun 26 04:14:11 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff1b80c5

dev-ruby/css_parser: add ruby24

Package-Manager: Portage-2.3.6, Repoman-2.3.1

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

diff --git a/dev-ruby/css_parser/css_parser-1.5.0.ebuild b/dev-ruby/css_parser/css_parser-1.5.0.ebuild
index 72c87f8f776..6fca6ba41cd 100644
--- a/dev-ruby/css_parser/css_parser-1.5.0.ebuild
+++ b/dev-ruby/css_parser/css_parser-1.5.0.ebuild
@@ -2,7 +2,7 @@
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
-USE_RUBY="ruby21 ruby22 ruby23"
+USE_RUBY="ruby21 ruby22 ruby23 ruby24"
 
 RUBY_FAKEGEM_RECIPE_DOC="rdoc"
 RUBY_FAKEGEM_DOC_DIR="doc"


             reply	other threads:[~2017-06-26  4:14 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26  4:14 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-10 15:56 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/css_parser/ Hans de Graaff
2025-03-10 15:56 Hans de Graaff
2024-12-14  7:47 Hans de Graaff
2024-12-13 11:48 Hans de Graaff
2024-10-14  5:56 Hans de Graaff
2024-10-14  5:56 Hans de Graaff
2024-08-24  7:58 Hans de Graaff
2024-08-24  7:58 Hans de Graaff
2024-04-09  5:27 Hans de Graaff
2024-04-07  5:53 Hans de Graaff
2024-04-07  5:53 Hans de Graaff
2024-03-08  8:09 Hans de Graaff
2023-09-09 10:34 Hans de Graaff
2023-08-30  5:25 Hans de Graaff
2023-01-13  7:57 Hans de Graaff
2022-12-24 15:00 Hans de Graaff
2022-12-24 15:00 Hans de Graaff
2021-12-14  6:57 Hans de Graaff
2021-12-14  6:57 Hans de Graaff
2021-07-31  6:47 Hans de Graaff
2021-07-07  6:53 Hans de Graaff
2020-08-22  7:56 Hans de Graaff
2020-07-23 15:02 Hans de Graaff
2019-12-02  8:37 Hans de Graaff
2019-02-12 18:17 Hans de Graaff
2018-05-30  4:33 Hans de Graaff
2018-04-30 20:11 Hans de Graaff
2018-02-25 22:01 Sergei Trofimovich
2018-02-02 17:14 Hans de Graaff
2017-09-10  5:59 Hans de Graaff
2017-09-10  5:59 Hans de Graaff
2017-04-20  5:03 Hans de Graaff
2017-03-10  6:44 Hans de Graaff
2017-03-10  6:44 Hans de Graaff
2017-02-23  6:56 Hans de Graaff
2017-02-05  9:18 Hans de Graaff
2016-12-01  7:46 Hans de Graaff
2016-12-01  7:46 Hans de Graaff
2016-10-21  4:46 Hans de Graaff
2016-10-21  4:46 Hans de Graaff
2016-10-12  4:53 Hans de Graaff
2016-06-30  5:21 Hans de Graaff
2016-06-28  4:39 Hans de Graaff
2016-06-19  5:20 Hans de Graaff
2016-06-19  5:20 Hans de Graaff
2016-03-22 21:31 Manuel Rüger
2016-03-16 23:20 Manuel Rüger
2016-03-16 23:20 Manuel Rüger
2016-02-27 10:10 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=1498450451.ff1b80c5b2468dc63a940691b495145e07876bbf.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