public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/argon2/
Date: Thu, 30 Aug 2018 08:45:22 +0000 (UTC)	[thread overview]
Message-ID: <1535618652.a96e3f7ecdd3d86f98c762fdb82b4b3cc771f19f.zlogene@gentoo> (raw)

commit:     a96e3f7ecdd3d86f98c762fdb82b4b3cc771f19f
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 30 08:44:12 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Aug 30 08:44:12 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a96e3f7e

app-crypt/argon2: amd64 stable wrt bug #664556

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 app-crypt/argon2/argon2-20171227.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-crypt/argon2/argon2-20171227.ebuild b/app-crypt/argon2/argon2-20171227.ebuild
index 4cf2b3b572c..e5b800c4faf 100644
--- a/app-crypt/argon2/argon2-20171227.ebuild
+++ b/app-crypt/argon2/argon2-20171227.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://github.com/P-H-C/phc-winner-argon2/archive/${PV}.tar.gz -> ${P}
 
 LICENSE="|| ( Apache-2.0 CC0-1.0 )"
 SLOT="0/1"
-KEYWORDS="~amd64 ~arm64 x86"
+KEYWORDS="amd64 ~arm64 x86"
 IUSE="static-libs"
 
 S="${WORKDIR}/phc-winner-${P}"


             reply	other threads:[~2018-08-30  8:45 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  8:45 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-29 14:45 [gentoo-commits] repo/gentoo:master commit in: app-crypt/argon2/ Sam James
2022-05-19  2:03 Sam James
2022-05-05 23:48 WANG Xuerui
2022-01-30 11:33 James Le Cuirot
2021-12-07 19:33 Sam James
2021-01-11 19:01 Fabian Groffen
2020-12-08 21:55 Sam James
2020-04-08 20:40 Göktürk Yüksek
2020-01-01 22:00 Michał Górny
2020-01-01 19:43 Agostino Sarubbo
2019-12-31 17:45 Michał Górny
2019-12-31  8:18 Agostino Sarubbo
2019-12-31  8:15 Agostino Sarubbo
2019-12-30 15:30 Agostino Sarubbo
2019-12-30 12:29 Agostino Sarubbo
2019-12-29  9:00 Mikle Kolyada
2019-12-28 19:44 Michał Górny
2019-12-28 12:31 Sergei Trofimovich
2019-12-28 10:17 Sergei Trofimovich
2019-12-27 23:15 Aaron Bauman
2019-12-27 16:43 Agostino Sarubbo
2019-10-26 20:35 Sergei Trofimovich
2019-10-23 15:54 Michał Górny
2019-10-23  8:14 Michał Górny
2019-10-23  8:14 Michał Górny
2019-10-23  8:14 Michał Górny
2019-07-31  9:04 Agostino Sarubbo
2019-07-18 10:04 Agostino Sarubbo
2019-07-18 10:03 Agostino Sarubbo
2019-05-12 22:03 Sergei Trofimovich
2019-05-10  4:41 Markus Meier
2019-05-07  6:26 Sergei Trofimovich
2019-04-17 11:49 Mikle Kolyada
2019-04-15 23:55 Aaron Bauman
2019-03-16  4:55 Michael Palimaka
2019-01-08 21:32 Jeroen Roovers
2018-12-30 18:16 Mikle Kolyada
2018-12-06 15:51 Mikle Kolyada
2018-10-24  4:10 Matt Turner
2018-10-17 15:57 Tobias Klausmann
2018-09-22 11:31 Sergei Trofimovich
2018-09-22 11:12 Sergei Trofimovich
2018-09-21  7:02 Sergei Trofimovich
2018-09-20 18:39 Michał Górny
2018-08-29  1:07 Thomas Deutschmann
2018-03-19 18:06 Guilherme Amadio
2018-01-02 17:21 Thomas Deutschmann
2018-01-02 15:50 Craig Andrews
2017-12-21  5:45 Markus Meier
2017-08-21  2:20 Michał Górny
2017-02-02 15:13 Thomas Deutschmann

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=1535618652.a96e3f7ecdd3d86f98c762fdb82b4b3cc771f19f.zlogene@gentoo \
    --to=zlogene@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