From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] dev/graaff:master commit in: dev-ruby/code_analyzer/
Date: Mon, 22 Aug 2016 19:01:00 +0000 (UTC) [thread overview]
Message-ID: <1471889586.4e796e0f07c3b98e60ff36c2d41bdf6445c1c90f.graaff@gentoo> (raw)
commit: 4e796e0f07c3b98e60ff36c2d41bdf6445c1c90f
Author: Hans de Graaff <hans <AT> degraaff <DOT> org>
AuthorDate: Mon Aug 22 18:13:06 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Aug 22 18:13:06 2016 +0000
URL: https://gitweb.gentoo.org/dev/graaff.git/commit/?id=4e796e0f
dev-ruby/code_analyzer: fix repoman warnings
Package-Manager: portage-2.2.28
dev-ruby/code_analyzer/code_analyzer-0.4.5.ebuild | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev-ruby/code_analyzer/code_analyzer-0.4.5.ebuild b/dev-ruby/code_analyzer/code_analyzer-0.4.5.ebuild
index 3db13d3..f270478 100644
--- a/dev-ruby/code_analyzer/code_analyzer-0.4.5.ebuild
+++ b/dev-ruby/code_analyzer/code_analyzer-0.4.5.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2014 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: $
+# $Id$
EAPI=5
-USE_RUBY="ruby19 ruby20 ruby21"
+USE_RUBY="ruby20 ruby21"
RUBY_FAKEGEM_EXTRADOC="README.md"
next reply other threads:[~2016-08-22 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 19:01 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-22 19:00 [gentoo-commits] dev/graaff:master commit in: dev-ruby/code_analyzer/ Hans de Graaff
2016-08-22 19:00 Hans de Graaff
2014-09-26 9:12 Hans de Graaff
2014-04-22 16:54 Hans de Graaff
2013-10-25 9:08 Hans de Graaff
2013-06-21 11:37 Hans de Graaff
2012-12-31 14:27 Hans de Graaff
2012-11-20 10:00 Hans de Graaff
2012-10-08 13:37 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=1471889586.4e796e0f07c3b98e60ff36c2d41bdf6445c1c90f.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