Low - In hgfelog.py, the MetaChange detection is too simplistic: a duplicate modification on a second branch shows up as a MetaChange because the file rev on the other branch is re-used. hgsubversion and hgconvert both produce commits from svn merges that have filerevs whose linkrev is not the current commit.
- In FishEye, we create a new revision, but it's parent rev is the last content change revsions parent, instead of the last content change revision, because that's what mercurial stores in it's filectx. We'd have to detect that and cope with it.
- In FE, a subsequent content mod will also have as it's parent the previous content mod revision, instead of the perm change revision, again, because that's what mercurial stores.
- relates to
-
FE-3325 HG: Add basic Mercurial Slurp tests
- Closed
