public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/hashalot/
Date: Wed, 19 Mar 2025 02:17:59 +0000 (UTC)	[thread overview]
Message-ID: <1742350642.35c51c94ca17bfe22ef0b60069f48292370e7175.sam@gentoo> (raw)

commit:     35c51c94ca17bfe22ef0b60069f48292370e7175
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 19 02:17:22 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 19 02:17:22 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=35c51c94

app-crypt/hashalot: Stabilize 0.3-r3 x86, #951582

Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-crypt/hashalot/hashalot-0.3-r3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-crypt/hashalot/hashalot-0.3-r3.ebuild b/app-crypt/hashalot/hashalot-0.3-r3.ebuild
index 583493b642ab..d78cd46ceea2 100644
--- a/app-crypt/hashalot/hashalot-0.3-r3.ebuild
+++ b/app-crypt/hashalot/hashalot-0.3-r3.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://www.paranoiacs.org/~sluskyb/hacks/hashalot/${P}.tar.gz"
 
 LICENSE="GPL-2+"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm ~hppa ~m68k ~mips ~ppc ppc64 ~s390 sparc ~x86"
+KEYWORDS="~alpha amd64 arm ~hppa ~m68k ~mips ~ppc ppc64 ~s390 sparc x86"
 
 src_prepare() {
 	default


             reply	other threads:[~2025-03-19  2:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19  2:17 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-19  2:02 [gentoo-commits] repo/gentoo:master commit in: app-crypt/hashalot/ Sam James
2025-03-19  2:02 Sam James
2025-03-19  2:02 Sam James
2025-03-19  1:21 Sam James
2025-02-13 12:19 Sam James
2019-12-01 18:42 Aaron Bauman
2019-10-18 12:19 David Seifert

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=1742350642.35c51c94ca17bfe22ef0b60069f48292370e7175.sam@gentoo \
    --to=sam@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