[PATCH 2 of 2] keyword: add: SVN-like keywords and config section to select their use

[Kevin Grover]

On Thu, Feb 4, 2010 at 1:15 AM, Christian Ebert <blacktrash at gmx.net> wrote:

> * Kevin Grover on Wednesday, February 03, 2010 at 17:08:46 -0600
> > On Wed, Feb 3, 2010 at 3:40 AM, Christian Ebert <blacktrash at gmx.net>
> wrote:
> >> I'm fine with the filters, but I must admit that personally I'm
> >> not keen on adding more config sections and more -- albeit
> >> optional -- templates, as I wasn't a friend of default templates
> >> in the first place.
> >>
> >> The same can be done in a (global) hgrc file already.
> >
> > I agree.  However, it must be done for each repository, each time.
>
> No. As long as you don't have to fear inadvertent expansions,
> e.g. /etc/mercurial/hgrc or ~/.hgrc works fine system-wide or at
> $HOME.
>
> > Granted, the keywords still have to be turned on (and the style set to
> SVN
> > for subversion keywords), however, if they're in keyword.py, they will be
> > consistent across all repositories.
>
> Same with a system-wide hgrc.
>
>
Granted.  However, only one set of keywords (those for CVS or those for SVN)
are active by default.  It would make it much easier for someone to convert
from SVN to Hg (and use keywords very close to how they were using them in
svn).  If someone wants custom keywords, they're still welcome to do
whatever they want.

By default, if they don't explicitly asked for svn keywords, nothing changes
from the way things are now (except for the use of os.sep in file names.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100204/91a67a4e/attachment.htm>