From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-vim/uptime/
Date: Sat, 28 Jan 2017 14:32:02 +0000 (UTC) [thread overview]
Message-ID: <1485613905.cc0e51d46fb6d100bb50c6b32621c9897fbb6ac1.leio@gentoo> (raw)
commit: cc0e51d46fb6d100bb50c6b32621c9897fbb6ac1
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 28 14:28:43 2017 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Jan 28 14:31:45 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc0e51d4
app-vim/uptime: Drop to ~mips; mips doesn't do stable keywords right now
Package-Manager: Portage-2.3.3, Repoman-2.3.1
app-vim/uptime/uptime-1.3-r1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-vim/uptime/uptime-1.3-r1.ebuild b/app-vim/uptime/uptime-1.3-r1.ebuild
index d9d4fb0..5000af4 100644
--- a/app-vim/uptime/uptime-1.3-r1.ebuild
+++ b/app-vim/uptime/uptime-1.3-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
@@ -9,7 +9,7 @@ inherit vim-plugin
DESCRIPTION="vim plugin: display vim uptimes"
HOMEPAGE="http://www.vim.org/scripts/script.php?script_id=965"
LICENSE="vim"
-KEYWORDS="alpha amd64 ia64 mips ppc sparc x86"
+KEYWORDS="alpha amd64 ia64 ~mips ppc sparc x86"
IUSE=""
VIM_PLUGIN_HELPFILES="uptime"
next reply other threads:[~2017-01-28 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 14:32 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-13 18:50 [gentoo-commits] repo/gentoo:master commit in: app-vim/uptime/ Michał Górny
2023-12-10 10:02 Arthur Zamarin
2023-12-09 20:16 Arthur Zamarin
2023-12-09 20:13 Arthur Zamarin
2023-12-09 19:57 Arthur Zamarin
2023-09-14 21:23 Conrad Kostecki
2018-03-10 22:55 Patrice Clement
2016-05-13 8:38 Patrice Clement
2016-05-13 8:38 Patrice Clement
2016-04-09 11:04 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=1485613905.cc0e51d46fb6d100bb50c6b32621c9897fbb6ac1.leio@gentoo \
--to=leio@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