patch: refactor file creation/removal detection The patcher has to know if a file is being created or removed to check if the target already exists, or to actually unlink the file when a hunk emptying it is applied. This was done by embedding the creation/removal information in the first (and only) hunk attached to the file. There are two problems with this approach: - creation/removal is really a property of the file being patched and not its hunk. - for regular patches, file creation cannot be deduced at parsing time: there are case where the *stripped* file paths must be compared. Modifying hunks after their creation is clumsy and prevent further refactorings related to copies handling. Instead, we delegate this job to selectfile() which has all the relevant information, and remove the hunk createfile() and rmfile() methods. [ original upstream message ]

     1

$Id$

     2

     3

keyword extension for Mercurial SCM

     4

===================================

     5

     6

CAVEAT: Please use the keyword extension distributed with

     7

Mercurial > 1.0.2!

     8

For Mercurial 0.9.2 to 1.0.2 install the 0.9.2compat branch.

     9

    10

The default and stable branches are meant for development.

    11

    12

install

    13

-------

    14

    15

Run "python setup.py install".

    16

See also "pyton setup.py --help".

    17

Then add the line:

    18

    19

[extensions]

    20

keyword = /path/to/hgkw/keyword.py

    21

    22

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

    23

    24

    25

first steps and online help

    26

---------------------------

    27

    28

$ hg help keyword 

    29

$ hg kwdemo

    30

    31

    32

testing

    33

-------

    34

    35

$ cd tests

    36

$ ./run-tests.py --with-hg=/path/to/hg