From: "Hans de Graaff (graaff)" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-ruby/kissfft: ChangeLog kissfft-0.0.2.ebuild
Date: Sun, 1 Feb 2015 15:39:27 +0000 (UTC) [thread overview]
Message-ID: <20150201153927.E16F210D44@oystercatcher.gentoo.org> (raw)
graaff 15/02/01 15:39:27
Modified: ChangeLog kissfft-0.0.2.ebuild
Log:
Add ruby22.
(Portage version: 2.2.14/cvs/Linux x86_64, signed Manifest commit with key 0x8883FA56A308A8D7!)
Revision Changes Path
1.10 dev-ruby/kissfft/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/kissfft/ChangeLog?rev=1.10&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/kissfft/ChangeLog?rev=1.10&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/kissfft/ChangeLog?r1=1.9&r2=1.10
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-ruby/kissfft/ChangeLog,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- ChangeLog 26 Sep 2014 06:38:01 -0000 1.9
+++ ChangeLog 1 Feb 2015 15:39:27 -0000 1.10
@@ -1,6 +1,9 @@
# ChangeLog for dev-ruby/kissfft
-# Copyright 1999-2014 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-ruby/kissfft/ChangeLog,v 1.9 2014/09/26 06:38:01 graaff Exp $
+# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/dev-ruby/kissfft/ChangeLog,v 1.10 2015/02/01 15:39:27 graaff Exp $
+
+ 01 Feb 2015; Hans de Graaff <graaff@gentoo.org> kissfft-0.0.2.ebuild:
+ Add ruby22.
*kissfft-0.0.2 (26 Sep 2014)
1.2 dev-ruby/kissfft/kissfft-0.0.2.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/kissfft/kissfft-0.0.2.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/kissfft/kissfft-0.0.2.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/kissfft/kissfft-0.0.2.ebuild?r1=1.1&r2=1.2
Index: kissfft-0.0.2.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-ruby/kissfft/kissfft-0.0.2.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- kissfft-0.0.2.ebuild 26 Sep 2014 06:38:01 -0000 1.1
+++ kissfft-0.0.2.ebuild 1 Feb 2015 15:39:27 -0000 1.2
@@ -1,10 +1,10 @@
-# Copyright 1999-2014 Gentoo Foundation
+# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/dev-ruby/kissfft/kissfft-0.0.2.ebuild,v 1.1 2014/09/26 06:38:01 graaff Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-ruby/kissfft/kissfft-0.0.2.ebuild,v 1.2 2015/02/01 15:39:27 graaff Exp $
EAPI=5
-USE_RUBY="ruby19 ruby20 ruby21"
+USE_RUBY="ruby19 ruby20 ruby21 ruby22"
RUBY_FAKEGEM_TASK_DOC=""
RUBY_FAKEGEM_TASK_TEST=""
next reply other threads:[~2015-02-01 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 15:39 Hans de Graaff (graaff) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-26 6:38 [gentoo-commits] gentoo-x86 commit in dev-ruby/kissfft: ChangeLog kissfft-0.0.2.ebuild Hans de Graaff (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=20150201153927.E16F210D44@oystercatcher.gentoo.org \
--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