D5961: copies: add test that makes both the merging csets dirty and run w/o error

Mon Mar 4 01:57:18 EST 2019

martinvonz added inline comments.

INLINE COMMENTS

> test-copies.t:495-497
> +Test for a case in fullcopytracing algorithm where both the merging csets are
> +dirty which means no cset is descendant of merging base. This test reflect
> +that for this particular case this algorithm correctly find the copies:

I don't follow this. What does "dirty" mean here? We normally mean that there are changes in the working copy when we say dirty, but that's clearly not what you mean here. The commit message is similarly confusing to me.

REPOSITORY
  rHG Mercurial

REVISION DETAIL
  https://phab.mercurial-scm.org/D5961

To: khanchi97, #hg-reviewers
Cc: martinvonz, mercurial-devel