From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rails-html-sanitizer/
Date: Sat, 30 Mar 2019 09:30:56 +0000 (UTC) [thread overview]
Message-ID: <1553938246.0e4865d7b42ac3b67ae4693b135bd0211e6e3de8.graaff@gentoo> (raw)
commit: 0e4865d7b42ac3b67ae4693b135bd0211e6e3de8
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 30 08:19:26 2019 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Mar 30 09:30:46 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e4865d7
dev-ruby/rails-html-sanitizer: add ruby26
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11
dev-ruby/rails-html-sanitizer/rails-html-sanitizer-1.0.4.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-ruby/rails-html-sanitizer/rails-html-sanitizer-1.0.4.ebuild b/dev-ruby/rails-html-sanitizer/rails-html-sanitizer-1.0.4.ebuild
index b62c22dbc2a..0d58ebcc8e2 100644
--- a/dev-ruby/rails-html-sanitizer/rails-html-sanitizer-1.0.4.ebuild
+++ b/dev-ruby/rails-html-sanitizer/rails-html-sanitizer-1.0.4.ebuild
@@ -1,8 +1,8 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=5
-USE_RUBY="ruby23 ruby24 ruby25"
+USE_RUBY="ruby23 ruby24 ruby25 ruby26"
RUBY_FAKEGEM_RECIPE_DOC="rdoc"
RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
next reply other threads:[~2019-03-30 9:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 9:30 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-07 7:32 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rails-html-sanitizer/ Hans de Graaff
2024-12-16 6:19 Hans de Graaff
2024-12-03 14:09 Hans de Graaff
2024-06-01 5:41 Hans de Graaff
2024-01-24 9:23 Hans de Graaff
2023-07-12 1:14 Sam James
2023-06-03 8:49 Hans de Graaff
2023-06-03 8:49 Hans de Graaff
2023-04-03 3:03 Sam James
2023-01-21 7:20 Hans de Graaff
2022-12-21 7:34 Hans de Graaff
2022-12-18 9:08 Hans de Graaff
2022-12-13 18:36 Hans de Graaff
2022-09-04 10:54 Hans de Graaff
2022-06-24 10:04 Hans de Graaff
2022-06-24 10:04 Hans de Graaff
2022-06-10 4:54 Hans de Graaff
2022-06-10 4:54 Hans de Graaff
2022-03-25 10:22 Hans de Graaff
2021-11-08 2:51 Yixun Lan
2021-08-24 5:59 Hans de Graaff
2021-08-19 6:33 Hans de Graaff
2021-03-11 10:54 Hans de Graaff
2020-12-20 19:14 Sam James
2020-12-20 19:03 Sam James
2020-09-11 4:06 Hans de Graaff
2020-04-20 20:41 Sergei Trofimovich
2020-03-12 10:57 Hans de Graaff
2019-10-07 5:46 Hans de Graaff
2019-10-07 5:46 Hans de Graaff
2019-10-01 18:06 Hans de Graaff
2019-08-24 7:36 Hans de Graaff
2019-08-05 5:17 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2018-05-14 18:50 Hans de Graaff
2018-04-11 18:50 Markus Meier
2018-03-24 8:35 Hans de Graaff
2018-01-14 8:15 Hans de Graaff
2017-08-25 6:09 Hans de Graaff
2017-07-02 5:43 Hans de Graaff
2016-12-29 13:06 Hans de Graaff
2016-07-18 6:49 Hans de Graaff
2016-07-18 6:49 Hans de Graaff
2016-05-18 8:56 Fabian Groffen
2016-02-16 21:14 Hans de Graaff
2016-02-06 8:11 Hans de Graaff
2016-01-26 6:39 Hans de Graaff
2016-01-26 6:39 Hans de Graaff
2016-01-17 8:22 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=1553938246.0e4865d7b42ac3b67ae4693b135bd0211e6e3de8.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