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

1 files updated, 0 files merged, 0 files removed, 0 files unresolved

     2

a

     3

checking changesets

     4

checking manifests

     5

crosschecking files in changesets and manifests

     6

checking files

     7

1 files, 1 changesets, 1 total revisions

     8

a not present

     9

checking changesets

    10

checking manifests

    11

crosschecking files in changesets and manifests

    12

checking files

    13

1 files, 1 changesets, 1 total revisions

    14

destination directory: a

    15

1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    16

a