public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/gr-osmosdr/
Date: Sat, 19 Nov 2022 01:07:15 +0000 (UTC)	[thread overview]
Message-ID: <1668819998.48c33c3a8a67d3d670e97ba4a1fddfd156292605.dlan@gentoo> (raw)

commit:     48c33c3a8a67d3d670e97ba4a1fddfd156292605
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 19 01:06:38 2022 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sat Nov 19 01:06:38 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=48c33c3a

net-wireless/gr-osmosdr: Keyword 0.2.3_p20210128-r1 riscv, #881733

Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>

 net-wireless/gr-osmosdr/gr-osmosdr-0.2.3_p20210128-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-wireless/gr-osmosdr/gr-osmosdr-0.2.3_p20210128-r1.ebuild b/net-wireless/gr-osmosdr/gr-osmosdr-0.2.3_p20210128-r1.ebuild
index f4e53404df69..b45e7c5a004e 100644
--- a/net-wireless/gr-osmosdr/gr-osmosdr-0.2.3_p20210128-r1.ebuild
+++ b/net-wireless/gr-osmosdr/gr-osmosdr-0.2.3_p20210128-r1.ebuild
@@ -16,7 +16,7 @@ else
 	COMMIT="a100eb024c0210b95e4738b6efd836d48225bd03"
 	SRC_URI="https://github.com/osmocom/gr-osmosdr/archive/${COMMIT}.tar.gz -> ${P}.tar.gz"
 	S="${WORKDIR}/${PN}-${COMMIT}"
-	KEYWORDS="~amd64 ~arm ~x86"
+	KEYWORDS="~amd64 ~arm ~riscv ~x86"
 fi
 
 LICENSE="GPL-3"


             reply	other threads:[~2022-11-19  1:07 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  1:07 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-22 14:54 [gentoo-commits] repo/gentoo:master commit in: net-wireless/gr-osmosdr/ Thomas Beierlein
2024-05-31 10:43 Thomas Beierlein
2024-01-03 19:31 Rick Farina
2024-01-03 19:31 Rick Farina
2024-01-03 19:31 Rick Farina
2023-12-16  3:04 Rick Farina
2023-04-06  2:18 Rick Farina
2023-04-04 23:55 Sam James
2023-02-17 22:26 Rick Farina
2023-02-17 22:26 Rick Farina
2023-01-25  6:10 Sam James
2023-01-25  6:10 Sam James
2023-01-25  6:10 Sam James
2023-01-25  6:10 Sam James
2023-01-25  6:10 Sam James
2022-11-22 16:42 Thomas Beierlein
2022-11-22  7:16 Thomas Beierlein
2022-11-22  7:16 Thomas Beierlein
2022-11-18  6:38 Arthur Zamarin
2022-08-29 12:08 Thomas Beierlein
2022-08-18 17:51 Thomas Beierlein
2022-07-19  1:50 Sam James
2022-07-19  1:50 Sam James
2022-06-10 13:45 Thomas Beierlein
2021-06-02 17:31 Rick Farina
2021-03-25 18:29 Rick Farina
2021-02-15  2:19 Rick Farina
2020-12-18 19:41 Rick Farina
2020-11-24 18:22 Rick Farina
2020-10-11 14:33 Mikle Kolyada
2020-09-04 16:22 Rick Farina
2020-09-04 16:22 Rick Farina
2020-09-04 16:22 Rick Farina
2020-06-01 20:45 Rick Farina
2020-02-09 16:34 Michał Górny
2019-12-04  0:25 Rick Farina
2019-08-28 16:14 Rick Farina
2019-07-03  5:22 Rick Farina
2018-11-07 20:01 Rick Farina
2018-11-07 20:01 Rick Farina
2018-08-25 19:22 Christian Ruppert
2018-08-16 20:45 Richard Farina
2018-08-16 20:45 Richard Farina
2018-06-06  8:17 Andreas Sturmlechner
2018-06-06  8:13 Andreas Sturmlechner
2018-02-22  3:14 Richard Farina
2018-02-19 17:29 Richard Farina
2015-12-19 14:04 Chí-Thanh Christopher Nguyễn

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=1668819998.48c33c3a8a67d3d670e97ba4a1fddfd156292605.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