public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: xfce-extra/xfce4-cpufreq-plugin/
Date: Fri, 25 Mar 2022 07:49:33 +0000 (UTC)	[thread overview]
Message-ID: <1648194544.354d4e3f0fb49dc79d02f4e391853488d66cb9c5.ago@gentoo> (raw)

commit:     354d4e3f0fb49dc79d02f4e391853488d66cb9c5
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 25 07:49:04 2022 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Fri Mar 25 07:49:04 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=354d4e3f

xfce-extra/xfce4-cpufreq-plugin: x86 stable wrt bug #835945

Package-Manager: Portage-3.0.30, Repoman-3.0.3
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 xfce-extra/xfce4-cpufreq-plugin/xfce4-cpufreq-plugin-1.2.7.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xfce-extra/xfce4-cpufreq-plugin/xfce4-cpufreq-plugin-1.2.7.ebuild b/xfce-extra/xfce4-cpufreq-plugin/xfce4-cpufreq-plugin-1.2.7.ebuild
index 1ebde5b0e8eb..b47899efafef 100644
--- a/xfce-extra/xfce4-cpufreq-plugin/xfce4-cpufreq-plugin-1.2.7.ebuild
+++ b/xfce-extra/xfce4-cpufreq-plugin/xfce4-cpufreq-plugin-1.2.7.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://archive.xfce.org/src/panel-plugins/${PN}/${PV%.*}/${P}.tar.bz2"
 
 LICENSE="GPL-2+"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ppc64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~ppc ppc64 ~riscv x86"
 
 RDEPEND=">=dev-libs/glib-2.20:=
 	>=x11-libs/gtk+-3.20:3=


             reply	other threads:[~2022-03-25  7:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  7:49 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-17 10:57 [gentoo-commits] repo/gentoo:master commit in: xfce-extra/xfce4-cpufreq-plugin/ Michał Górny
2023-03-17  8:56 Arthur Zamarin
2023-03-15  6:55 Michał Górny
2023-02-03 16:53 Sam James
2023-02-03 14:21 Arthur Zamarin
2022-11-03 14:50 Michał Górny
2022-03-25 20:56 Michał Górny
2022-03-25 19:44 Sam James
2022-03-25  7:47 Agostino Sarubbo
2022-03-24 19:03 Jakov Smolić
2022-02-02  7:13 Michał Górny
2022-01-29 19:32 Michał Górny
2021-04-15 20:44 Michał Górny
2021-04-13 18:23 Sergei Trofimovich
2021-04-11 11:11 Sam James
2021-04-11 11:06 Sam James
2021-04-09 22:22 Sam James
2021-03-02 20:07 Michał Górny
2021-02-18 22:08 Sam James
2021-02-08  6:11 Sam James
2021-02-08  6:05 Sam James
2021-02-02 23:01 Michał Górny
2021-01-12  9:49 Michał Górny
2021-01-05 21:59 Andreas K. Hüttel
2020-10-31 20:20 Sergei Trofimovich
2020-10-31 20:16 Sergei Trofimovich
2020-10-31 16:27 Thomas Deutschmann
2020-10-15 18:05 Michał Górny
2019-04-07  8:29 Michał Górny
2018-11-24 13:40 Sergei Trofimovich
2018-11-18 16:01 Sergei Trofimovich
2018-11-15 17:04 Thomas Deutschmann
2018-11-12 13:52 Mikle Kolyada
2018-11-11 19:07 Michał Górny
2018-09-24 16:29 Michał Górny
2018-05-27 20:56 Mikle Kolyada
2018-05-18  6:54 Denis Dupeyron
2018-04-18 21:04 Sergei Trofimovich
2018-04-08 17:28 Aaron Bauman
2017-05-17  7:21 Michał Górny
2016-08-02 16:10 Michał Górny
2016-06-23 15:07 Michał Górny

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=1648194544.354d4e3f0fb49dc79d02f4e391853488d66cb9c5.ago@gentoo \
    --to=ago@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