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: app-misc/vifm/
Date: Sun, 20 Sep 2015 09:30:14 +0000 (UTC)	[thread overview]
Message-ID: <1442741331.a1f4493c970ff9f60843de2c7c1912c13a110762.ago@gentoo> (raw)

commit:     a1f4493c970ff9f60843de2c7c1912c13a110762
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 20 09:28:51 2015 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Sep 20 09:28:51 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a1f4493c

app-misc/vifm: x86 stable wrt bug #558026

Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="x86"

 app-misc/vifm/vifm-0.8.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-misc/vifm/vifm-0.8.ebuild b/app-misc/vifm/vifm-0.8.ebuild
index 78e5318..7e3c38a 100644
--- a/app-misc/vifm/vifm-0.8.ebuild
+++ b/app-misc/vifm/vifm-0.8.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://sourceforge/vifm/${P}.tar.bz2"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="amd64 ppc ~s390 ~x86"
+KEYWORDS="amd64 ppc ~s390 x86"
 IUSE="X developer +extended-keys gtk +magic vim vim-syntax"
 
 DEPEND="


             reply	other threads:[~2015-09-20  9:30 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20  9:30 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-10  8:22 [gentoo-commits] repo/gentoo:master commit in: app-misc/vifm/ Petr Vaněk
2024-10-09  0:06 Jakov Smolić
2024-10-06  8:26 Sam James
2024-10-06  7:59 Sam James
2024-09-04 10:53 Petr Vaněk
2024-04-30 22:56 Sam James
2024-04-30 22:56 Sam James
2024-04-30 22:55 Sam James
2023-05-05  4:39 Sam James
2023-05-05  4:39 Sam James
2022-06-30 18:44 Sam James
2022-06-30 18:44 Sam James
2022-06-11  5:36 Sam James
2022-02-27 15:36 Patrice Clement
2021-10-19  0:56 Sam James
2021-03-21 19:43 Patrice Clement
2021-01-18 11:36 David Seifert
2021-01-08 10:36 Sam James
2021-01-07 16:52 Sam James
2020-12-28 11:50 David Seifert
2019-11-27 23:29 Patrice Clement
2019-11-27 23:29 Patrice Clement
2019-10-01 21:38 Patrice Clement
2019-08-11  8:13 Michał Górny
2019-05-23 20:21 Patrice Clement
2018-11-13 19:20 José María Alonso
2018-11-13  8:40 José María Alonso
2018-05-25 23:58 Thomas Deutschmann
2018-05-24 14:31 Agostino Sarubbo
2018-05-20 16:47 Mikle Kolyada
2018-05-20 16:47 Mikle Kolyada
2018-04-07 15:30 José María Alonso
2018-02-05 21:44 José María Alonso
2018-01-27 18:56 José María Alonso
2017-12-03 19:29 José María Alonso
2017-10-15 12:53 Sergei Trofimovich
2017-08-29 23:16 Thomas Deutschmann
2017-07-31 12:56 Tobias Klausmann
2017-06-21 11:36 José María Alonso
2017-06-20 15:01 José María Alonso
2017-04-06 18:06 José María Alonso
2016-08-15 16:29 José María Alonso
2016-08-13 20:50 José María Alonso
2016-07-06  9:23 Agostino Sarubbo
2016-06-25 20:14 Agostino Sarubbo
2016-04-28 11:14 José María Alonso
2016-03-26 16:39 Agostino Sarubbo
2016-03-04 16:37 José María Alonso
2016-02-23 11:00 José María Alonso
2016-02-22 21:41 José María Alonso
2016-01-09 19:48 José María Alonso
2015-09-06 13:25 Agostino Sarubbo
2015-08-26 10:43 Agostino Sarubbo

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=1442741331.a1f4493c970ff9f60843de2c7c1912c13a110762.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