From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/bear/
Date: Sat, 22 Oct 2022 11:26:07 +0000 (UTC) [thread overview]
Message-ID: <1666437925.c1e3aeb20227963a187af9b7f38c7e27e4ac44be.dlan@gentoo> (raw)
commit: c1e3aeb20227963a187af9b7f38c7e27e4ac44be
Author: Xin Yang <yangmame <AT> icloud <DOT> com>
AuthorDate: Sat Oct 22 09:44:41 2022 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sat Oct 22 11:25:25 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c1e3aeb2
dev-util/bear: keyword 3.0.19 riscv, #877899
Closes: https://github.com/gentoo/gentoo/pull/27892
Signed-off-by: Xin Yang <yangmame <AT> icloud.com>
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>
dev-util/bear/bear-3.0.19.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/bear/bear-3.0.19.ebuild b/dev-util/bear/bear-3.0.19.ebuild
index 71c521da77db..9ac6d7e10574 100644
--- a/dev-util/bear/bear-3.0.19.ebuild
+++ b/dev-util/bear/bear-3.0.19.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/rizsotto/Bear/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="GPL-3+"
SLOT="0"
-KEYWORDS="~amd64 ~ppc64 ~x86"
+KEYWORDS="~amd64 ~ppc64 ~riscv ~x86"
IUSE="test"
RDEPEND="
next reply other threads:[~2022-10-22 11:26 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 11:26 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-03 14:35 [gentoo-commits] repo/gentoo:master commit in: dev-util/bear/ Arthur Zamarin
2025-04-27 21:16 Sam James
2025-02-11 20:54 Andreas Sturmlechner
2024-12-31 4:57 Sam James
2024-12-31 3:19 Jakov Smolić
2024-11-18 9:07 Petr Vaněk
2024-11-18 9:07 Petr Vaněk
2024-09-14 9:53 Florian Schmaus
2024-09-13 19:33 Arthur Zamarin
2024-09-13 19:33 Arthur Zamarin
2024-08-13 13:05 Joonas Niilola
2024-07-03 5:30 Joonas Niilola
2024-05-12 15:41 Sam James
2024-05-12 15:41 Sam James
2024-04-01 7:14 Sam James
2024-03-16 13:34 Joonas Niilola
2023-09-15 6:06 Sam James
2023-07-07 10:14 Sam James
2023-07-07 4:40 Sam James
2023-06-06 6:41 Sam James
2023-04-25 14:56 Arthur Zamarin
2023-02-16 5:52 WANG Xuerui
2023-02-07 2:59 Sam James
2022-12-21 23:09 Sam James
2022-11-10 7:58 Sam James
2022-07-06 19:33 Sam James
2022-07-04 17:56 Georgy Yakovlev
2022-07-04 17:56 Georgy Yakovlev
2022-04-08 5:25 Georgy Yakovlev
2021-12-24 12:08 Georgy Yakovlev
2021-12-24 12:08 Georgy Yakovlev
2021-12-20 4:19 Georgy Yakovlev
2021-10-17 0:03 Georgy Yakovlev
2021-10-12 16:13 Georgy Yakovlev
2021-10-07 5:34 Georgy Yakovlev
2021-07-14 21:27 Georgy Yakovlev
2021-07-04 9:48 Georgy Yakovlev
2021-07-04 9:10 Georgy Yakovlev
2021-07-03 20:40 Georgy Yakovlev
2021-07-03 20:38 Georgy Yakovlev
2021-06-23 3:47 Georgy Yakovlev
2021-06-09 6:04 Georgy Yakovlev
2021-06-04 23:15 Georgy Yakovlev
2021-05-07 7:35 Joonas Niilola
2021-05-07 7:35 Joonas Niilola
2021-05-03 17:01 Georgy Yakovlev
2021-04-23 20:06 Georgy Yakovlev
2021-04-23 19:50 Georgy Yakovlev
2021-04-23 5:55 Joonas Niilola
2021-04-22 4:07 Georgy Yakovlev
2021-04-22 4:07 Georgy Yakovlev
2021-04-22 4:07 Georgy Yakovlev
2021-04-06 10:10 Joonas Niilola
2021-04-06 10:08 Joonas Niilola
2020-09-10 22:58 Georgy Yakovlev
2020-07-01 21:23 Georgy Yakovlev
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=1666437925.c1e3aeb20227963a187af9b7f38c7e27e4ac44be.dlan@gentoo \
--to=dlan@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