From: "Patrice Clement" <monsieurp@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-vim/udev-syntax/
Date: Sat, 16 Dec 2017 23:31:30 +0000 (UTC) [thread overview]
Message-ID: <1513467083.6ea2460b74c73bfdc642b907f8b373a58bb295d9.monsieurp@gentoo> (raw)
commit: 6ea2460b74c73bfdc642b907f8b373a58bb295d9
Author: Patrice Clement <monsieurp <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 16 21:29:25 2017 +0000
Commit: Patrice Clement <monsieurp <AT> gentoo <DOT> org>
CommitDate: Sat Dec 16 23:31:23 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6ea2460b
app-vim/udev-syntax: stable for amd64. mark stable for the remaining arches using the ALLARCHES policy.
Package-Manager: Portage-2.3.13, Repoman-2.3.3
app-vim/udev-syntax/udev-syntax-20051016-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-vim/udev-syntax/udev-syntax-20051016-r2.ebuild b/app-vim/udev-syntax/udev-syntax-20051016-r2.ebuild
index 68ed0060b73..77a1748c27a 100644
--- a/app-vim/udev-syntax/udev-syntax-20051016-r2.ebuild
+++ b/app-vim/udev-syntax/udev-syntax-20051016-r2.ebuild
@@ -8,7 +8,7 @@ inherit vim-plugin
DESCRIPTION="vim plugin: syntax highlighting for udev rules files"
HOMEPAGE="http://www.vim.org/scripts/script.php?script_id=1381"
LICENSE="vim"
-KEYWORDS="~amd64 ~hppa ~mips ~ppc ~sparc ~x86"
+KEYWORDS="amd64 hppa ~mips ppc sparc x86"
VIM_PLUGIN_HELPTEXT=\
"This plugin provides syntax highlighting for udev.rules files. These files
next reply other threads:[~2017-12-16 23:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 23:31 Patrice Clement [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/udev-syntax/ Michał Górny
2023-12-09 20:56 Arthur Zamarin
2023-12-09 20:36 Arthur Zamarin
2023-12-09 20:06 Arthur Zamarin
2023-12-09 19:57 Arthur Zamarin
2023-09-14 21:23 Conrad Kostecki
2018-03-10 22:55 Patrice Clement
2017-12-16 23:31 Patrice Clement
2017-08-09 21:26 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=1513467083.6ea2460b74c73bfdc642b907f8b373a58bb295d9.monsieurp@gentoo \
--to=monsieurp@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