From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/usbredir/
Date: Mon, 29 Apr 2024 13:42:01 +0000 (UTC) [thread overview]
Message-ID: <1714397986.81d994573d0867240d5ee54e3f0b2fead5e5b542.sam@gentoo> (raw)
commit: 81d994573d0867240d5ee54e3f0b2fead5e5b542
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 29 13:39:46 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 29 13:39:46 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=81d99457
sys-apps/usbredir: Stabilize 0.14.0 x86, #930871
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-apps/usbredir/usbredir-0.14.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-apps/usbredir/usbredir-0.14.0.ebuild b/sys-apps/usbredir/usbredir-0.14.0.ebuild
index 1aee1c945bc4..b58616004f15 100644
--- a/sys-apps/usbredir/usbredir-0.14.0.ebuild
+++ b/sys-apps/usbredir/usbredir-0.14.0.ebuild
@@ -12,7 +12,7 @@ S="${WORKDIR}"/usbredir-${P}
LICENSE="GPL-2 LGPL-2.1"
SLOT="0"
-KEYWORDS="~alpha ~amd64 arm arm64 ~ia64 ~loong ppc ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm arm64 ~ia64 ~loong ppc ppc64 ~riscv ~sparc x86"
IUSE="test"
RESTRICT="!test? ( test )"
next reply other threads:[~2024-04-29 13:42 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 13:42 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-29 13:42 [gentoo-commits] repo/gentoo:master commit in: sys-apps/usbredir/ Sam James
2024-03-12 4:04 Sam James
2024-03-12 4:04 Sam James
2023-10-04 15:28 Sam James
2023-08-27 14:13 David Seifert
2023-05-05 10:14 Sam James
2022-12-25 21:24 Sam James
2022-12-25 20:31 Arthur Zamarin
2022-12-25 20:19 Arthur Zamarin
2022-12-25 20:13 Sam James
2022-12-25 20:13 Sam James
2022-12-25 20:07 Arthur Zamarin
2022-10-29 21:39 Sam James
2022-09-23 5:41 Sam James
2022-02-26 8:33 Joonas Niilola
2022-02-25 21:43 Sam James
2022-02-25 20:44 Arthur Zamarin
2022-02-25 18:32 Sam James
2022-02-25 18:32 Sam James
2022-02-25 10:11 Joonas Niilola
2022-02-25 10:11 Joonas Niilola
2022-02-17 12:17 Joonas Niilola
2022-02-17 12:17 Joonas Niilola
2022-01-23 8:05 Yixun Lan
2021-05-26 8:33 David Seifert
2021-05-26 8:11 Sam James
2021-05-26 8:04 Sam James
2021-05-24 0:12 Sam James
2021-05-24 0:12 Sam James
2021-05-23 23:05 Agostino Sarubbo
2021-05-23 22:28 Agostino Sarubbo
2021-04-21 19:02 Sam James
2021-04-04 18:35 Matthias Maier
2021-04-04 18:35 Matthias Maier
2021-04-04 18:35 Matthias Maier
2020-08-19 22:40 Sam James
2020-03-15 18:41 Agostino Sarubbo
2020-03-15 18:34 Agostino Sarubbo
2020-03-15 18:31 Agostino Sarubbo
2020-03-15 18:29 Agostino Sarubbo
2020-03-15 18:27 Agostino Sarubbo
2020-03-15 18:26 Agostino Sarubbo
2020-02-15 10:03 David Seifert
2019-07-28 19:39 Matthias Maier
2018-06-10 3:41 Matthias Maier
2018-04-18 18:15 David Seifert
2018-02-12 3:05 Matthias Maier
2018-02-12 3:05 Matthias Maier
2017-08-17 17:06 Michał Górny
2017-05-22 1:21 Michael Weber
2017-05-17 19:20 Markus Meier
2017-05-12 17:56 Tobias Klausmann
2017-05-04 13:07 Agostino Sarubbo
2017-05-03 12:55 Matthias Maier
2017-05-03 12:55 Matthias Maier
2017-05-03 12:55 Matthias Maier
2017-05-03 12:55 Matthias Maier
2015-12-07 18:17 Robin H. Johnson
2015-12-07 18:17 Robin H. Johnson
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=1714397986.81d994573d0867240d5ee54e3f0b2fead5e5b542.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