# HG changeset patch
# User Christian Ebert <blacktrash@gmx.net>
# Date 1249484515 -7200
# Node ID 439e096ce144ebd0a0e5ad82524ca7c92616c8c0
# Parent  d0185236a0892cb40802fa49c9213967c81d0217
(0.9.2compat) remove "help keyword" from test

diff -r d0185236a089 -r 439e096ce144 tests/test-keyword
--- a/tests/test-keyword	Mon Aug 03 11:49:46 2009 +0200
+++ b/tests/test-keyword	Wed Aug 05 17:01:55 2009 +0200
@@ -12,11 +12,6 @@
 commit.test=cp a hooktest
 EOF
 
-echo % help
-# grep for backwards compatibility
-hg help keyword \
-| grep -E -v '^list of commands|hg -v help keyword|^$'
-
 echo % hg kwdemo
 hg --quiet kwdemo --default \
 | sed -e 's![^ ][^ ]*demo.txt,v!/TMP/demo.txt,v!' \
diff -r d0185236a089 -r 439e096ce144 tests/test-keyword.out
--- a/tests/test-keyword.out	Mon Aug 03 11:49:46 2009 +0200
+++ b/tests/test-keyword.out	Wed Aug 05 17:01:55 2009 +0200
@@ -1,44 +1,3 @@
-% help
-keyword extension - expand keywords in tracked files
-This extension expands RCS/CVS-like or self-customized $Keywords$ in tracked
-text files selected by your configuration.
-Keywords are only expanded in local repositories and not stored in the change
-history. The mechanism can be regarded as a convenience for the current user
-or for archive distribution.
-Configuration is done in the [keyword] and [keywordmaps] sections of hgrc
-files.
-Example:
-    [keyword]
-    # expand keywords in every python file except those matching "x*"
-    **.py =
-    x*    = ignore
-NOTE: the more specific you are in your filename patterns the less you lose
-speed in huge repositories.
-For [keywordmaps] template mapping and expansion demonstration and control run
-"hg kwdemo".
-An additional date template filter {date|utcdate} is provided.
-The default template mappings (view with "hg kwdemo -d") can be replaced with
-customized keywords and templates. Again, run "hg kwdemo" to control the
-results of your config changes.
-Before changing/disabling active keywords, run "hg kwshrink" to avoid the risk
-of inadvertently storing expanded keywords in the change history.
-To force expansion after enabling it, or a configuration change, run "hg
-kwexpand".
-Also, when committing with the record extension or using mq's qrecord, be
-aware that keywords cannot be updated. Again, run "hg kwexpand" on the files
-in question to update keyword expansions after all changes have been checked
-in.
-Expansions spanning more than one line and incremental expansions, like CVS'
-$Log$, are not supported. A keyword template map "Log = {desc}" expands to the
-first line of the changeset description.
-Caveat: With Mercurial versions prior to 4574925db5c0 "hg import" might
-        cause rejects if the patch context contains an active keyword. In that
-        case run "hg kwshrink", and then reimport. Or, better, use
-        bundle/unbundle to share changes.
- kwdemo     print [keywordmaps] configuration and an expansion example
- kwexpand   expand keywords in the working directory
- kwfiles    show files configured for keyword expansion
- kwshrink   revert expanded keywords in the working directory
 % hg kwdemo
 [extensions]
 hgext.keyword =