public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-misc/fortune-mod/
Date: Wed,  4 May 2022 22:54:37 +0000 (UTC)	[thread overview]
Message-ID: <1651704868.6920c0fc335866cc874c3b5a753a5cef767d9aa2.jsmolic@gentoo> (raw)

commit:     6920c0fc335866cc874c3b5a753a5cef767d9aa2
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Wed May  4 22:48:45 2022 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Wed May  4 22:54:28 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6920c0fc

games-misc/fortune-mod: Keyword 3.14.0 x86, #842504

Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>

 games-misc/fortune-mod/fortune-mod-3.14.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/games-misc/fortune-mod/fortune-mod-3.14.0.ebuild b/games-misc/fortune-mod/fortune-mod-3.14.0.ebuild
index 99bf1ef27861..4928b4a09ccb 100644
--- a/games-misc/fortune-mod/fortune-mod-3.14.0.ebuild
+++ b/games-misc/fortune-mod/fortune-mod-3.14.0.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://www.shlomifish.org/open-source/projects/${PN}/arcs/${P}.tar.xz
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~m68k ~mips ~riscv"
+KEYWORDS="~amd64 ~m68k ~mips ~riscv ~x86"
 IUSE="offensive test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2022-05-04 22:54 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 22:54 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-07  5:15 [gentoo-commits] repo/gentoo:master commit in: games-misc/fortune-mod/ Sam James
2023-12-12  6:30 Viorel Munteanu
2023-09-29  0:54 Sam James
2023-09-28 22:49 Sam James
2023-09-28 22:49 Sam James
2023-09-28 22:49 Sam James
2023-09-28 22:49 Sam James
2023-09-28 22:49 Sam James
2023-07-05 20:49 Conrad Kostecki
2023-04-14 19:43 Sam James
2023-03-17 20:06 Sam James
2023-02-24 22:20 Sam James
2023-02-22 17:17 Arthur Zamarin
2023-02-22 17:13 Arthur Zamarin
2023-02-22 16:50 Sam James
2023-02-22 16:10 Sam James
2023-02-22 16:10 Sam James
2023-02-22 16:10 Sam James
2022-08-27 11:25 Sam James
2022-08-13 13:32 Sam James
2022-05-07 12:54 Arthur Zamarin
2022-05-06 20:03 Arthur Zamarin
2022-05-05  6:13 Arthur Zamarin
2022-05-05  5:57 Arthur Zamarin
2022-05-05  5:57 Arthur Zamarin
2022-05-05  5:39 Arthur Zamarin
2022-05-04 10:41 Yixun Lan
2022-05-03 19:47 Arthur Zamarin
2022-05-03 19:47 Arthur Zamarin
2022-05-01 12:20 Jakov Smolić
2022-02-15 18:31 Matt Turner
2022-01-24 19:19 Sam James
2022-01-21 20:12 Arthur Zamarin
2022-01-21 12:42 Sam James
2022-01-03 23:26 David Seifert
2022-01-02 17:49 David Seifert
2021-12-29  7:43 Sam James
2021-12-16  7:36 Sam James
2021-12-07  6:14 Joshua Kinard
2021-12-06  2:44 Yixun Lan
2021-12-05 21:41 James Le Cuirot
2021-12-04 11:23 Arthur Zamarin
2021-12-04 10:07 Arthur Zamarin
2021-12-04  4:13 Sam James
2021-12-04  0:54 Sam James
2021-12-03 20:47 Arthur Zamarin
2021-12-03 14:20 Arthur Zamarin
2021-12-03  3:10 Sam James
2021-01-06 23:02 Fabian Groffen
2020-05-16 14:36 Mike Gilbert
2018-06-28 14:22 Mikle Kolyada
2017-07-08 13:19 Alexis Ballier

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=1651704868.6920c0fc335866cc874c3b5a753a5cef767d9aa2.jsmolic@gentoo \
    --to=jsmolic@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