convert: add a mode where mercurial_sink skips empty revisions. The getchanges function of some converter_source classes can return some false positives. I.e. they sometimes claim that a file "foo" was changed in some revision, even though its contents are still the same. convert_svn is particularly bad, but I think this can also happen with convert_cvs and, at least in theory, with mercurial_source. For regular conversions this is not really a problem - as long as getfile returns the right contents, we'll get a converted revision with the right contents. But when we use --filemap, this could lead to superfluous revisions being converted. Instead of fixing every converter_source, I decided to change mercurial_sink to work around this problem. When --filemap is used, we're interested only in revisions that touch some specific files. If a revision doesn't change any of these files, then we're not interested in it (at least for revisions with a single parent; merges are special). For mercurial_sink, we abuse this property and rollback a commit if the manifest text hasn't changed. This avoids duplicating the logic from localrepo.filecommit to detect unchanged files.

     1

1:016807e6fdaf

     2

0:eb43f19ff115

     3

016807e6fdaf tip

     4

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

     5

eb43f19ff115

     6

eb43f19ff115+

     7

reverting file1

     8

? file1.orig

     9

eb43f19ff115

    10

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

    11

? file1.orig

    12

016807e6fdaf tip

    13

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

    14

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

    15

? file1.orig

    16

016807e6fdaf tip

    17

? file1.orig

    18

016807e6fdaf tip

    19

? file1.orig

    20

016807e6fdaf tip

    21

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

    22

? file1.orig

    23

016807e6fdaf tip