public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/ofono/
Date: Tue, 30 Jan 2024 15:19:30 +0000 (UTC)	[thread overview]
Message-ID: <1706627946.2bbf57f566b66bc4cf1d7c84e2bb925902257039.sam@gentoo> (raw)

commit:     2bbf57f566b66bc4cf1d7c84e2bb925902257039
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 30 15:19:06 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jan 30 15:19:06 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2bbf57f5

net-misc/ofono: Stabilize 2.1 amd64, #923338

Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-misc/ofono/ofono-2.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-misc/ofono/ofono-2.1.ebuild b/net-misc/ofono/ofono-2.1.ebuild
index 65a8744990af..a2f38c1e6145 100644
--- a/net-misc/ofono/ofono-2.1.ebuild
+++ b/net-misc/ofono/ofono-2.1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://mirrors.edge.kernel.org/pub/linux/network/${PN}/${P}.tar.xz"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~amd64 arm ~arm64 ~hppa ~loong ppc ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="amd64 arm ~arm64 ~hppa ~loong ppc ppc64 ~riscv ~sparc ~x86"
 IUSE="+atmodem bluetooth +cdmamodem +datafiles doc dundee examples +isimodem +phonesim +provision +qmimodem tools +udev upower"
 
 REQUIRED_USE="dundee? ( bluetooth )"


             reply	other threads:[~2024-01-30 15:19 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 15:19 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-11 12:40 [gentoo-commits] repo/gentoo:master commit in: net-misc/ofono/ Yixun Lan
2024-07-11 10:05 Yixun Lan
2024-01-31  9:33 Yixun Lan
2024-01-31  9:31 Yixun Lan
2024-01-31  0:39 Yixun Lan
2024-01-30 15:19 Sam James
2024-01-30 15:19 Sam James
2024-01-30 15:01 Sam James
2024-01-30 15:01 Sam James
2024-01-30 15:01 Sam James
2024-01-30 12:53 Yixun Lan
2024-01-30 12:53 Yixun Lan
2023-08-28  3:18 Yixun Lan
2023-08-01 16:14 Sam James
2023-01-20 12:21 Yixun Lan
2022-05-19  5:08 WANG Xuerui
2022-03-29 12:54 Yixun Lan
2022-03-29 12:54 Yixun Lan
2022-02-04  7:23 Agostino Sarubbo
2022-02-04  7:22 Agostino Sarubbo
2022-02-03  6:03 Sam James
2022-02-02  9:47 Sam James
2022-02-02  9:47 Sam James
2022-02-02  9:47 Sam James
2022-02-02  1:19 Yixun Lan
2021-09-24  2:57 Yixun Lan
2021-08-30 23:29 Marek Szuba
2020-12-23 22:57 Sam James
2020-12-21  9:36 Sergei Trofimovich
2020-12-02 23:37 Sam James
2020-12-02 14:57 Sam James
2020-11-29  8:25 Agostino Sarubbo
2020-11-29  8:22 Agostino Sarubbo
2020-11-29  8:20 Agostino Sarubbo
2020-11-29  8:16 Agostino Sarubbo
2020-11-27 16:49 Thomas Deutschmann
2019-11-16 10:45 Yixun Lan
2019-11-16 10:42 Yixun Lan
2019-10-21  1:39 Yixun Lan
2019-05-15  4:48 Aaron Bauman
2019-04-25  3:10 Yixun Lan
2019-04-25  3:10 Yixun Lan
2019-02-13  8:07 Yixun Lan
2018-08-13  4:16 Yixun Lan
2018-04-20 14:06 Yixun Lan
2018-04-20 14:06 Yixun Lan
2018-04-20 14:06 Yixun Lan
2017-06-20 12:12 Alexis Ballier
2017-06-05  9:54 Yixun Lan
2016-11-01  2:50 Yixun Lan
2016-05-27  7:17 Yixun Lan

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=1706627946.2bbf57f566b66bc4cf1d7c84e2bb925902257039.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