From: "Sebastian Pipping" <sping@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/emacs-tools:gentoo-syntax commit in: /
Date: Sun, 6 May 2012 16:06:20 +0000 (UTC) [thread overview]
Message-ID: <1327174661.5c7eef3bdc79d58f0c0e4d7d091830ba3d765203.sping@gentoo> (raw)
commit: 5c7eef3bdc79d58f0c0e4d7d091830ba3d765203
Author: Christian Faulhammer <fauli <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 21 19:37:41 2012 +0000
Commit: Sebastian Pipping <sping <AT> gentoo <DOT> org>
CommitDate: Sat Jan 21 19:37:41 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/emacs-tools.git;a=commit;h=5c7eef3b
gentoo-syntax: (ebuild-mode-keywords-savedconfig) Add savedconfig_pkg_postinst() function
svn path=/gentoo-syntax/; revision=1713
---
ChangeLog | 5 +++++
ebuild-mode-keywords.el | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index fdab673..26ecdd9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2012-01-21 Christian Faulhammer <fauli@gentoo.org>
+
+ * ebuild-mode-keywords.el (ebuild-mode-keywords-savedconfig): Add
+ savedconfig_pkg_postinst() function
+
2011-12-31 Ulrich Mueller <ulm@gentoo.org>
* keyword-generation.sh: Set C locale for grep. Reformat output.
diff --git a/ebuild-mode-keywords.el b/ebuild-mode-keywords.el
index 35f2e11..726c469 100644
--- a/ebuild-mode-keywords.el
+++ b/ebuild-mode-keywords.el
@@ -620,7 +620,7 @@ font-lock-type-face))
font-lock-type-face))
(defvar ebuild-mode-keywords-savedconfig
- '(("save_config" "restore_config")
+ '(("save_config" "restore_config" "savedconfig_pkg_postinst")
font-lock-type-face))
(defvar ebuild-mode-keywords-scons-utils
next reply other threads:[~2012-05-06 16:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 16:06 Sebastian Pipping [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-04 19:21 [gentoo-commits] proj/emacs-tools:gentoo-syntax commit in: / Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-01-13 21:15 Ulrich Mueller
2013-01-13 21:15 Ulrich Mueller
2012-09-22 22:47 Ulrich Mueller
2012-09-22 21:26 Ulrich Mueller
2012-09-22 21:26 Ulrich Mueller
2012-09-22 20:48 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-06-09 13:10 Ulrich Mueller
2012-05-06 18:47 Ulrich Mueller
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
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=1327174661.5c7eef3bdc79d58f0c0e4d7d091830ba3d765203.sping@gentoo \
--to=sping@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