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

checking changesets

     2

checking manifests

     3

crosschecking files in changesets and manifests

     4

checking files

     5

1 files, 1 changesets, 1 total revisions

     6

checking changesets

     7

checking manifests

     8

crosschecking files in changesets and manifests

     9

checking files

    10

verify failed

    11

checking changesets

    12

checking manifests

    13

crosschecking files in changesets and manifests

    14

checking files

    15

1 files, 1 changesets, 1 total revisions

    16

commit failed