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: x11-drivers/xf86-input-evdev/
Date: Wed, 25 Jan 2017 12:28:15 +0000 (UTC)	[thread overview]
Message-ID: <1485347184.68196d728e5a1045d16888dd6256dfc688ede3a0.ago@gentoo> (raw)

commit:     68196d728e5a1045d16888dd6256dfc688ede3a0
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 25 12:26:24 2017 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Jan 25 12:26:24 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=68196d72

x11-drivers/xf86-input-evdev: ppc64 stable wrt bug #579266

Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 x11-drivers/xf86-input-evdev/xf86-input-evdev-2.10.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x11-drivers/xf86-input-evdev/xf86-input-evdev-2.10.3.ebuild b/x11-drivers/xf86-input-evdev/xf86-input-evdev-2.10.3.ebuild
index e4bab6c..665ed8e 100644
--- a/x11-drivers/xf86-input-evdev/xf86-input-evdev-2.10.3.ebuild
+++ b/x11-drivers/xf86-input-evdev/xf86-input-evdev-2.10.3.ebuild
@@ -6,7 +6,7 @@ EAPI=5
 inherit linux-info xorg-2
 
 DESCRIPTION="Generic Linux input driver"
-KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~mips ppc ~ppc64 ~sh sparc x86"
+KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~mips ppc ppc64 ~sh sparc x86"
 IUSE=""
 
 RDEPEND=">=x11-base/xorg-server-1.18[udev]


             reply	other threads:[~2017-01-25 12:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 12:28 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-23 21:16 [gentoo-commits] repo/gentoo:master commit in: x11-drivers/xf86-input-evdev/ Matt Turner
2024-11-18  9:36 Sam James
2024-11-17 21:03 Michał Górny
2024-11-17 16:00 Michał Górny
2024-11-17 16:00 Michał Górny
2024-11-17 16:00 Michał Górny
2024-11-17 16:00 Michał Górny
2024-11-17 16:00 Michał Górny
2024-10-18  2:40 Matt Turner
2022-05-25 16:02 WANG Xuerui
2022-01-03 21:01 James Le Cuirot
2021-07-21  5:48 Yixun Lan
2021-03-19 22:40 David Seifert
2020-12-14 21:51 Sergei Trofimovich
2019-01-20  6:52 Matt Turner
2019-01-20  5:43 Matt Turner
2018-08-08 19:25 Matt Turner
2018-08-08 19:25 Matt Turner
2018-08-08 19:25 Matt Turner
2018-08-08 19:25 Matt Turner
2018-07-27 23:18 Matt Turner
2018-07-27 23:18 Matt Turner
2018-07-17 14:15 Matt Turner
2018-07-17 14:15 Matt Turner
2018-05-29  2:43 Matt Turner
2017-03-16  8:15 Jeroen Roovers
2017-03-08  7:44 Michael Weber
2017-01-28  5:37 Matt Turner
2017-01-18  4:05 Matt Turner
2016-11-17 10:48 Agostino Sarubbo
2016-11-16 10:44 Agostino Sarubbo
2016-10-01 11:18 Manuel Rüger
2016-10-01 11:18 Manuel Rüger
2016-09-22 15:55 Tobias Klausmann
2016-08-05 23:29 Markus Meier
2016-08-03  4:32 Jeroen Roovers
2016-06-04  9:49 Chí-Thanh Christopher Nguyễn
2016-05-04 12:15 Manuel Rüger
2016-05-04 12:15 Manuel Rüger
2016-01-23 14:17 Manuel Rüger
2016-01-08 23:39 Manuel Rüger
2016-01-08 23:39 Manuel Rüger
2015-12-19 21:36 Markus Meier
2015-10-28 18:52 Manuel Rüger

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=1485347184.68196d728e5a1045d16888dd6256dfc688ede3a0.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