diff -r f88ecc1a41fa -r fe37939db543 hgkw/keyword.py --- a/hgkw/keyword.py Thu Feb 08 07:21:32 2007 +0100 +++ b/hgkw/keyword.py Thu Feb 08 14:28:00 2007 +0100 @@ -6,14 +6,14 @@ # of the GNU General Public License, incorporated herein by reference. # # $Id$ -# +# # Keyword expansion hack against the grain of a DSCM -# +# # There are many good reasons why this is not needed in a distributed # SCM, still it may be useful in very small projects based on single # files (like LaTeX packages), that are mostly addressed to an audience # not running a version control system. -# +# # For in-depth discussion refer to # . # @@ -22,7 +22,7 @@ # # The user has the choice either to create his own keywords and their # expansions or to use the CVS-like default ones. -# +# # Default $keywords$ and their $keyword: substition $ are: # Revision: changeset id # Author: username @@ -31,17 +31,17 @@ # Source: /path/to/basename,v # Id: basename,v csetid %Y/%m/%d %H:%M:%S username # Header: /path/to/basename,v csetid %Y/%m/%d %H:%M:%S username -# +# # Expansions spanning more than one line are truncated to their first line. # Incremental expansion (like CVS' $Log$) is not supported. -# +# # Simple setup in hgrc: -# +# # # enable extension # keyword = /full/path/to/keyword.py # # or, if script in hgext folder: # # hgext.keyword = -# +# # # filename patterns for expansion are configured in this section # # files matching patterns with value 'ignore' are ignored # [keyword] @@ -63,14 +63,14 @@ Keywords are only expanded in local repositories and not logged by Mercurial internally. The mechanism can be regarded as a convenience for the current user and may be turned off anytime. - + Substitution takes place on every commit and update of the working repository. Configuration is done in the [keyword] and [keywordmaps] sections of hgrc files. ''' - + from mercurial.i18n import gettext as _ # above line for backwards compatibility of standalone version from mercurial import commands, cmdutil, templater, util