From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/nasm/
Date: Tue, 3 Oct 2023 14:15:11 +0000 (UTC) [thread overview]
Message-ID: <1696342490.05cf971a5cadfb04ed5a7b6e2a6420a3de91dcff.sam@gentoo> (raw)
commit: 05cf971a5cadfb04ed5a7b6e2a6420a3de91dcff
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 3 14:14:50 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Oct 3 14:14:50 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=05cf971a
dev-lang/nasm: Stabilize 2.16.01-r1 amd64, #915106
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-lang/nasm/nasm-2.16.01-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-lang/nasm/nasm-2.16.01-r1.ebuild b/dev-lang/nasm/nasm-2.16.01-r1.ebuild
index a70aa0b349d7..ee599043c45c 100644
--- a/dev-lang/nasm/nasm-2.16.01-r1.ebuild
+++ b/dev-lang/nasm/nasm-2.16.01-r1.ebuild
@@ -12,7 +12,7 @@ S="${WORKDIR}"/${P/_}
LICENSE="BSD-2"
SLOT="0"
-KEYWORDS="~amd64 arm64 ~ia64 ~loong ppc64 ~riscv ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 arm64 ~ia64 ~loong ppc64 ~riscv ~x86 ~amd64-linux ~x86-linux"
IUSE="doc"
QA_CONFIG_IMPL_DECL_SKIP=(
next reply other threads:[~2023-10-03 14:15 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 14:15 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-04 17:31 [gentoo-commits] repo/gentoo:master commit in: dev-lang/nasm/ Arthur Zamarin
2024-08-04 3:16 Sam James
2024-08-03 22:51 Sam James
2024-08-03 16:48 Jakov Smolić
2024-08-03 16:48 Jakov Smolić
2024-08-03 11:06 Arthur Zamarin
2024-07-31 17:51 Matthew Smith
2024-04-21 10:25 Matthew Smith
2024-04-07 10:40 Matthew Smith
2023-10-22 14:34 Joonas Niilola
2023-10-03 14:15 Sam James
2023-10-03 12:06 Sam James
2023-10-03 12:06 Sam James
2022-12-23 10:04 Matthew Smith
2022-12-02 19:27 Arthur Zamarin
2022-12-02 18:50 Arthur Zamarin
2022-12-02 18:44 WANG Xuerui
2022-09-16 9:34 Joonas Niilola
2022-09-15 14:49 Matthew Smith
2022-09-15 7:05 Joonas Niilola
2021-08-31 23:55 Sam James
2021-08-14 5:59 Joonas Niilola
2021-07-30 8:55 Sergei Trofimovich
2020-10-08 8:00 Sergei Trofimovich
2020-09-06 8:34 Sergei Trofimovich
2020-09-01 20:12 Sam James
2020-08-29 14:48 Thomas Deutschmann
2020-08-28 19:04 Sergei Trofimovich
2020-08-21 8:03 Sergei Trofimovich
2020-07-25 9:18 Sergei Trofimovich
2020-07-21 23:15 Kent Fredric
2020-07-18 7:48 Sergei Trofimovich
2020-07-05 10:56 Sergei Trofimovich
2020-07-02 20:23 Sergei Trofimovich
2020-06-29 6:35 Sergei Trofimovich
2019-08-10 18:21 Aaron Bauman
2019-07-24 20:49 Thomas Deutschmann
2019-01-24 22:22 Thomas Deutschmann
2019-01-23 18:34 Mikle Kolyada
2019-01-15 9:28 Sergei Trofimovich
2018-11-11 10:54 Sergei Trofimovich
2018-11-11 10:54 Sergei Trofimovich
2018-06-10 16:26 Sergei Trofimovich
2018-05-11 7:41 Michał Górny
2018-05-11 6:35 Sergei Trofimovich
2018-05-10 22:09 Sergei Trofimovich
2018-02-26 14:25 Jason Zaman
2018-02-25 20:16 Thomas Deutschmann
2018-02-21 18:03 Michał Górny
2017-11-20 19:30 Sergei Trofimovich
2017-07-02 3:05 David Seifert
2016-05-13 14:51 Agostino Sarubbo
2016-04-20 4:45 Michael Sterrett
2016-04-04 15:18 Michael Sterrett
2016-03-03 6:15 Michael Sterrett
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=1696342490.05cf971a5cadfb04ed5a7b6e2a6420a3de91dcff.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