From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/polybar/
Date: Sat, 23 Jun 2018 17:51:05 +0000 (UTC) [thread overview]
Message-ID: <1529776256.c882ec3742cc5342b3f4e79861a2b39d9a976249.zlogene@gentoo> (raw)
commit: c882ec3742cc5342b3f4e79861a2b39d9a976249
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 23 17:50:56 2018 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sat Jun 23 17:50:56 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c882ec37
x11-misc/polybar: amd64 stable wrt bug #658142
Package-Manager: Portage-2.3.40, Repoman-2.3.9
x11-misc/polybar/polybar-3.1.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/polybar/polybar-3.1.0.ebuild b/x11-misc/polybar/polybar-3.1.0.ebuild
index 2e0573650b2..d2c4ebbf0f5 100644
--- a/x11-misc/polybar/polybar-3.1.0.ebuild
+++ b/x11-misc/polybar/polybar-3.1.0.ebuild
@@ -18,7 +18,7 @@ SRC_URI="https://github.com/jaagr/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 x86"
+KEYWORDS="amd64 x86"
IUSE="alsa curl i3wm ipc mpd network"
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
next reply other threads:[~2018-06-23 17:51 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 17:51 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-31 6:47 [gentoo-commits] repo/gentoo:master commit in: x11-misc/polybar/ John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28 18:51 John Helmert III
2024-05-11 19:08 Sam James
2024-05-11 19:08 Sam James
2024-01-08 5:50 John Helmert III
2024-01-08 5:50 John Helmert III
2023-11-27 18:12 John Helmert III
2023-11-20 14:36 John Helmert III
2023-06-11 19:00 John Helmert III
2023-06-11 7:37 Andreas Sturmlechner
2023-02-28 12:15 Yixun Lan
2022-10-08 2:56 John Helmert III
2022-10-08 2:56 John Helmert III
2022-10-08 2:56 John Helmert III
2022-09-10 0:48 Sam James
2022-09-09 17:24 John Helmert III
2022-07-19 16:44 John Helmert III
2022-07-06 0:20 Sam James
2022-07-05 20:09 John Helmert III
2022-05-04 13:59 John Helmert III
2022-04-04 18:51 John Helmert III
2022-03-05 15:37 John Helmert III
2022-03-03 5:23 John Helmert III
2022-03-02 1:42 John Helmert III
2022-01-30 1:47 John Helmert III
2022-01-30 1:47 John Helmert III
2021-11-01 10:02 Sam James
2021-11-01 2:07 Sam James
2021-09-22 23:49 John Helmert III
2021-09-22 23:49 John Helmert III
2021-07-17 18:18 David Seifert
2021-07-11 20:51 Sam James
2021-07-11 19:11 John Helmert III
2021-05-24 23:37 John Helmert III
2021-05-24 23:37 John Helmert III
2021-04-16 0:35 Sam James
2021-04-13 7:36 Agostino Sarubbo
2021-03-14 5:36 John Helmert III
2021-03-02 2:42 John Helmert III
2021-02-22 21:29 John Helmert III
2021-01-09 4:21 Sam James
2020-12-27 5:35 Sam James
2020-12-27 5:35 Sam James
2020-12-15 3:43 Sam James
2020-12-13 10:44 Joonas Niilola
2020-10-04 16:13 David Seifert
2020-10-04 16:13 David Seifert
2020-09-23 10:34 Agostino Sarubbo
2020-09-23 10:20 Agostino Sarubbo
2020-07-05 8:24 Joonas Niilola
2020-02-13 12:46 Agostino Sarubbo
2020-02-13 12:03 Agostino Sarubbo
2020-02-12 17:21 Johannes Huber
2020-01-14 22:48 Matt Turner
2020-01-13 20:08 Johannes Huber
2020-01-01 21:12 Johannes Huber
2020-01-01 21:12 Johannes Huber
2020-01-01 19:52 Johannes Huber
2020-01-01 19:52 Johannes Huber
2019-10-28 7:41 Agostino Sarubbo
2019-10-27 23:20 Thomas Deutschmann
2019-05-28 20:05 Johannes Huber
2019-05-28 20:05 Johannes Huber
2019-05-28 20:05 Johannes Huber
2018-10-06 21:43 Johannes Huber
2018-09-22 9:10 Michał Górny
2018-09-22 9:04 Michał Górny
2018-08-05 21:48 Patrice Clement
2018-07-23 15:56 Tony Vroon
2018-06-23 8:50 Johannes Huber
2018-06-17 23:29 Thomas Deutschmann
2018-06-14 21:17 Johannes Huber
2018-05-11 11:48 Johannes Huber
2018-05-11 10:55 Michał Górny
2018-05-04 21:05 Patrice Clement
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=1529776256.c882ec3742cc5342b3f4e79861a2b39d9a976249.zlogene@gentoo \
--to=zlogene@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