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

merging baz and foo

     2

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

     3

(branch merge, don't forget to commit)

     4

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

     5

merging foo and baz

     6

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

     7

(branch merge, don't forget to commit)

     8

initializing destination new repository

     9

scanning source...

    10

sorting...

    11

converting...

    12

4 add foo bar

    13

3 change foo

    14

2 make bar and baz copies of foo

    15

1 merge local copy

    16

0 merge remote copy

    17

comparing with ../orig

    18

searching for changes

    19

no changes found