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/bcrypt-ruby/
Date: Tue, 17 May 2022 05:32:28 +0000 (UTC)	[thread overview]
Message-ID: <1652765015.9b2c9e1ef7c0dc5cdedaf591ad78655017155bcb.graaff@gentoo> (raw)

commit:     9b2c9e1ef7c0dc5cdedaf591ad78655017155bcb
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Tue May 17 05:23:35 2022 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Tue May 17 05:23:35 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9b2c9e1e

dev-ruby/bcrypt-ruby: stabilize 3.1.17 for amd64

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

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

diff --git a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.17.ebuild b/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.17.ebuild
index 2d97b3822298..b4ec5e5c6220 100644
--- a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.17.ebuild
+++ b/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.17.ebuild
@@ -20,7 +20,7 @@ DESCRIPTION="An easy way to keep your users' passwords secure"
 HOMEPAGE="https://github.com/codahale/bcrypt-ruby"
 LICENSE="MIT"
 
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 SLOT="0"
 IUSE=""
 


             reply	other threads:[~2022-05-17  5:32 UTC|newest]

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