extensions: improve the consistency of synopses
Trying as much as possible to consistently:
- use a present tense predicate followed by a direct object
- verb referring directly to the functionality provided
(ie. not "add command that does this" but simple "do that")
- keep simple and to the point, leaving details for the long help
(width is tight, possibly even more so for translations)
Thanks to timeless, Martin Geisler, Rafael Villar Burke, Dan Villiom
Podlaski Christiansen and others for the helpful suggestions.
[ original upstream message ]
--- a/hgkw/keyword.py Sat Jun 20 20:57:13 2009 +0200
+++ b/hgkw/keyword.py Mon Jun 22 15:48:08 2009 +0200
@@ -26,7 +26,7 @@
#
# Run "hg help keyword" and "hg kwdemo" to get info on configuration.
-'''keyword expansion in tracked files
+'''expand keywords in tracked files
This extension expands RCS/CVS-like or self-customized $Keywords$ in
tracked text files selected by your configuration.
--- a/tests/test-keyword.out Sat Jun 20 20:57:13 2009 +0200
+++ b/tests/test-keyword.out Mon Jun 22 15:48:08 2009 +0200
@@ -1,5 +1,5 @@
% help
-keyword extension - keyword expansion in tracked files
+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.
@@ -55,9 +55,9 @@
enabled extensions:
- keyword keyword expansion in tracked files
- mq patch management and development
- notify hook extension to email notifications on commits/pushes
+ keyword expand keywords in tracked files
+ mq work with a stack of patches
+ notify send e-mail notifications for commits/pushes
use "hg -v help keyword" to show aliases and global options
% hg kwdemo