From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/mechanize/
Date: Mon, 13 Jun 2016 05:16:25 +0000 (UTC) [thread overview]
Message-ID: <1465794931.f749d28aab22b6ec6900e825944bcd17fa7c3b61.graaff@gentoo> (raw)
commit: f749d28aab22b6ec6900e825944bcd17fa7c3b61
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 13 05:15:31 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Jun 13 05:15:31 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f749d28a
dev-ruby/mechanize: mark ruby21 revision stable
Package-Manager: portage-2.2.28
dev-ruby/mechanize/mechanize-2.7.3-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/mechanize/mechanize-2.7.3-r1.ebuild b/dev-ruby/mechanize/mechanize-2.7.3-r1.ebuild
index 7c43261..8862ad3 100644
--- a/dev-ruby/mechanize/mechanize-2.7.3-r1.ebuild
+++ b/dev-ruby/mechanize/mechanize-2.7.3-r1.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="https://github.com/sparklemotion/mechanize"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~x86-solaris"
+KEYWORDS="amd64 ~ppc ~ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~x86-solaris"
IUSE=""
ruby_add_bdepend ">=dev-ruby/hoe-3.7
next reply other threads:[~2016-06-13 5:16 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 5:16 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 14:27 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/mechanize/ Sam James
2024-08-01 5:58 Hans de Graaff
2024-08-01 5:58 Hans de Graaff
2024-07-19 9:52 Hans de Graaff
2024-07-16 6:02 Hans de Graaff
2024-07-16 6:02 Hans de Graaff
2024-06-13 5:50 Hans de Graaff
2024-01-23 8:27 Hans de Graaff
2024-01-16 7:36 Hans de Graaff
2023-09-16 4:23 Hans de Graaff
2023-08-29 17:19 Hans de Graaff
2023-04-18 6:26 Hans de Graaff
2023-04-16 7:16 Hans de Graaff
2023-04-08 7:25 Hans de Graaff
2023-04-07 6:34 Hans de Graaff
2023-03-31 1:03 Sam James
2022-07-13 9:25 Hans de Graaff
2022-06-26 6:20 Hans de Graaff
2022-06-10 4:54 Hans de Graaff
2022-06-10 4:54 Hans de Graaff
2022-03-27 9:54 Hans de Graaff
2022-03-27 9:54 Hans de Graaff
2022-01-20 6:40 Hans de Graaff
2022-01-20 6:40 Hans de Graaff
2021-11-12 6:29 Hans de Graaff
2021-10-24 5:34 Hans de Graaff
2021-08-07 7:33 Hans de Graaff
2021-08-07 7:33 Hans de Graaff
2021-05-14 4:18 Hans de Graaff
2021-05-10 12:31 Sam James
2021-04-04 6:53 Hans de Graaff
2021-02-23 7:01 Hans de Graaff
2021-02-04 5:56 Hans de Graaff
2021-02-04 5:56 Hans de Graaff
2021-02-02 5:56 Hans de Graaff
2020-06-06 8:04 Hans de Graaff
2019-05-04 19:14 Hans de Graaff
2018-12-12 10:11 Hans de Graaff
2018-11-23 10:53 Hans de Graaff
2018-09-12 4:51 Hans de Graaff
2018-06-03 5:35 Hans de Graaff
2018-01-24 16:43 Hans de Graaff
2018-01-21 19:37 Hans de Graaff
2018-01-21 19:37 Hans de Graaff
2017-08-26 8:27 Hans de Graaff
2017-02-03 7:36 Hans de Graaff
2017-02-03 7:36 Hans de Graaff
2016-12-24 13:55 Manuel Rüger
2016-11-25 14:49 Hans de Graaff
2016-08-23 5:06 Hans de Graaff
2016-06-13 5:16 Hans de Graaff
2016-06-13 5:16 Hans de Graaff
2016-01-01 7: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=1465794931.f749d28aab22b6ec6900e825944bcd17fa7c3b61.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