README
author Adrian Buehlmann <adrian@cadifra.com>
Fri, 21 Mar 2008 14:52:24 +0100
branchstable
changeset 427 39fef460b62c
parent 321 ce5474dd2a9a
child 495 791e48d817e8
child 560 42502f8fc5b0
child 561 efeb09cb3760
permissions -rw-r--r--
clone: print "updating working directory" status message With this change, "hg clone" looks like this: % hg clone http://example.com/repo/big big requesting all changes adding changesets adding manifests adding file changes added XXX changesets with XXX changes to XXX files updating working directory XXX files updated, XXX files merged, XXX files removed, XXX files unresolved So the user sees % hg clone http://example.com/repo/big big requesting all changes adding changesets adding manifests adding file changes added XXX changesets with XXX changes to XXX files updating working directory while Mercurial is writing to disk to populate the working directory With this change, "hg clone" looks like this: % hg clone big big-work updating working directory XXX files updated, XXX files merged, XXX files removed, XXX files unresolved [ original upstream description ]

$Id$

keyword extension for Mercurial SCM
===================================

install
-------

Either copy hgkw/keyword.py into the hgext directory of your
Mercurial installation.
Then add the lines:

[extensions]
hgext.keyword =

to your hgrc file.

Or run "python setup.py install".
See also "pyton setup.py --help".
Then add the line:

[extensions]
keyword = /path/to/hgkw/keyword.py

to your hgrc, where /path/to/ is somewhere in your $PYTHONPATH.


first steps and online help
---------------------------

$ hg help keyword 
$ hg kwdemo


testing
-------

Copy hgkw/keyword.py into the hgext directory of your Mercurial
source tree. Copy tests/test-keyword, tests/test-keyword.out into
the tests directory of your Mercurial source tree. Change to that
directory and run:

$ python run-tests.py test-keyword

and then keep your fingers crossed ...