purge: abort with missing files avoiding problems with name-mangling fs In a name mangling filesystem (e.g. a case insensitive one) dirstate.walk() can yield filenames different from the ones stored in the dirstate. This already confuses the status and add commands, but with purge this may cause data loss. To prevent this purge refuses to work if there are missing files and has a 'force' option if the user knows it is safe. Even with the force option purge checks if any of the missing files is still available in the working dir: if so there may be some problem with the underlying filesystem, so it unconditionally aborts.

     1

#!/bin/sh

     2

     3

hg init a

     4

cd a

     5

touch empty1

     6

hg add empty1

     7

hg commit -m 'add empty1' -d '1000000 0'

     8

     9

touch empty2

    10

hg add empty2

    11

hg commit -m 'add empty2' -d '1000000 0'

    12

    13

hg up -C 0

    14

touch empty3

    15

hg add empty3

    16

hg commit -m 'add empty3' -d '1000000 0'

    17

    18

hg heads

    19

    20

hg merge 1

    21

# before changeset 05257fd28591, we didn't notice the 

    22

# empty file that came from rev 1.

    23

hg status

    24

hg commit -m merge -d '1000000 0'

    25

hg manifest --debug tip