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

pulling from source1

     2

requesting all changes

     3

adding changesets

     4

adding manifests

     5

adding file changes

     6

added 10 changesets with 10 changes to 1 files

     7

(run 'hg update' to get a working copy)

     8

requesting all changes

     9

adding changesets

    10

adding manifests

    11

adding file changes

    12

added 10 changesets with 10 changes to 1 files

    13

checking changesets

    14

checking manifests

    15

crosschecking files in changesets and manifests

    16

checking files

    17

1 files, 10 changesets, 10 total revisions

    18

checking changesets

    19

checking manifests

    20

crosschecking files in changesets and manifests

    21

checking files

    22

1 files, 10 changesets, 10 total revisions