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-libs/libqmi/
Date: Fri, 28 May 2021 19:11:23 +0000 (UTC)	[thread overview]
Message-ID: <1622229014.74c09b875227123e8e9dd328eb0ac6ccefb957f7.sam@gentoo> (raw)

commit:     74c09b875227123e8e9dd328eb0ac6ccefb957f7
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri May 28 19:10:14 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri May 28 19:10:14 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=74c09b87

net-libs/libqmi: Stabilize 1.28.4 arm, #792327

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

 net-libs/libqmi/libqmi-1.28.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-libs/libqmi/libqmi-1.28.4.ebuild b/net-libs/libqmi/libqmi-1.28.4.ebuild
index ae2df1d5549..60062c803a6 100644
--- a/net-libs/libqmi/libqmi-1.28.4.ebuild
+++ b/net-libs/libqmi/libqmi-1.28.4.ebuild
@@ -7,7 +7,7 @@ if [[ ${PV} == "9999" ]] ; then
 	inherit git-r3 autotools
 	EGIT_REPO_URI="https://gitlab.freedesktop.org/mobile-broadband/libqmi.git"
 else
-	KEYWORDS="~amd64 ~arm ~arm64 ~mips ~ppc ~ppc64 ~x86"
+	KEYWORDS="~amd64 arm ~arm64 ~mips ~ppc ~ppc64 ~x86"
 	SRC_URI="https://www.freedesktop.org/software/libqmi/${P}.tar.xz"
 fi
 


             reply	other threads:[~2021-05-28 19:11 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 19:11 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-13 13:51 [gentoo-commits] repo/gentoo:master commit in: net-libs/libqmi/ Andreas Sturmlechner
2024-10-09  8:23 Sam James
2024-05-29 11:48 Sam James
2024-05-29  6:26 Jakov Smolić
2024-05-28 22:01 Sam James
2023-07-29 11:51 Pacho Ramos
2023-07-29 11:51 Pacho Ramos
2023-07-09 12:29 Matt Turner
2022-10-31 14:28 Matt Turner
2022-08-15 19:13 Arthur Zamarin
2022-08-15 17:43 Arthur Zamarin
2022-07-29  2:59 Sam James
2022-06-24 15:33 Matt Turner
2022-06-24 15:33 Matt Turner
2022-05-31  9:24 Jakov Smolić
2022-05-28  5:05 Sam James
2022-05-24 11:14 WANG Xuerui
2022-05-24 11:14 WANG Xuerui
2022-04-28 15:31 Matt Turner
2022-03-09 15:39 Sam James
2022-03-09 12:49 Sam James
2022-03-08 12:32 Sam James
2022-02-11 20:56 Matt Turner
2022-01-24 22:43 Matt Turner
2021-11-06  3:58 Sam James
2021-10-04  1:24 Sam James
2021-09-15 20:27 Matt Turner
2021-08-08 19:46 Marek Szuba
2021-08-05 23:09 Matt Turner
2021-07-26  7:15 Matt Turner
2021-07-24 17:08 Sam James
2021-07-11 20:48 Sam James
2021-07-11  2:31 Sam James
2021-07-10 15:40 Sam James
2021-06-06 21:49 Matt Turner
2021-05-29 15:27 Sam James
2021-05-28 19:20 Sam James
2021-05-15 16:54 Matt Turner
2021-04-13 16:20 Matt Turner
2021-04-12 22:12 Sam James
2021-04-12 22:12 Sam James
2021-03-30  3:19 Matt Turner
2021-03-21 14:28 Matt Turner
2021-03-12 15:28 Sam James
2021-03-12  8:04 Mikle Kolyada
2021-03-11  2:35 Sam James
2021-01-08  2:46 Matt Turner
2021-01-08  2:34 Matt Turner
2019-12-24 14:55 Mikle Kolyada
2019-12-16  0:57 Aaron Bauman
2019-12-15 14:46 Agostino Sarubbo
2019-12-15 12:44 Agostino Sarubbo
2019-12-01 14:01 Sergei Trofimovich
2019-12-01 13:56 Sergei Trofimovich
2019-05-21  3:17 Aaron Bauman
2019-04-01 12:18 Tony Vroon
2018-12-05  7:34 Mikle Kolyada
2018-12-04 16:27 Mikle Kolyada
2018-11-06  7:41 Mikle Kolyada
2018-11-04 19:14 Thomas Deutschmann
2018-08-22 14:56 Tony Vroon
2017-10-29 16:24 Andreas Hüttel
2017-06-26  7:56 Alexis Ballier
2017-03-31 13:31 Michael Weber
2017-03-27 16:39 Jason Donenfeld
2017-02-17  5:58 Markus Meier
2016-12-29 18:53 Andreas Sturmlechner
2016-12-29 18:53 Andreas Sturmlechner
2016-12-21 18:56 Tobias Klausmann
2016-11-15 18:24 Mike Frysinger
2016-11-15 18:24 Mike Frysinger
2016-09-17 14:19 Tony Vroon
2016-03-31 13:24 Tony Vroon
2016-03-31 11:27 Alexey Shvetsov

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=1622229014.74c09b875227123e8e9dd328eb0ac6ccefb957f7.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