Patchwork D6373: tests: avoid the word "dirty" to mean "not a descendant of merge base"

login
register
mail settings
Submitter phabricator
Date May 14, 2019, 5:29 p.m.
Message ID <e4966fb2f75825dcd15c716cb8bc921f@localhost.localdomain>
Download mbox | patch
Permalink /patch/40022/
State Not Applicable
Headers show

Comments

phabricator - May 14, 2019, 5:29 p.m.
This revision was automatically updated to reflect the committed changes.
Closed by commit rHGcbff7f996dc4: tests: avoid the word &quot;dirty&quot; to mean &quot;not a descendant of merge base&quot; (authored by martinvonz, committed by ).

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST UPDATE
  https://phab.mercurial-scm.org/D6373?vs=15071&id=15075

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

AFFECTED FILES
  tests/test-copies.t

CHANGE DETAILS




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

Patch

diff --git a/tests/test-copies.t b/tests/test-copies.t
--- a/tests/test-copies.t
+++ b/tests/test-copies.t
@@ -504,9 +504,9 @@ 
   x -> z
 
 
-Test for a case in fullcopytracing algorithm where both the merging csets are
-"dirty"; where a dirty cset means that cset is descendant of merge base. This
-test reflect that for this particular case this algorithm correctly find the copies:
+Test for a case in fullcopytracing algorithm where neither of the merging csets
+is a descendant of the merge base. This test reflects that the algorithm
+correctly finds the copies:
 
   $ cat >> $HGRCPATH << EOF
   > [experimental]
@@ -565,8 +565,8 @@ 
       b
      +baba
   
-Test to make sure that fullcopytracing algorithm don't fail when both the merging csets are dirty
-(a dirty cset is one who is not the descendant of merge base)
+Test to make sure that fullcopytracing algorithm doesn't fail when neither of the
+merging csets is a descendant of the base.
 -------------------------------------------------------------------------------------------------
 
   $ newrepo
@@ -637,8 +637,8 @@ 
   o  0 added a
      a
 
-Now if we trigger a merge between cset revision 3 and 6 using base revision 4, in this case
-both the merging csets will be dirty as no one is descendent of base revision:
+Now if we trigger a merge between revision 3 and 6 using base revision 4,
+neither of the merging csets will be a descendant of the base revision:
 
   $ hg graft -r 6 --base 4 --hidden -t :other
   grafting 6:99802e4f1e46 "added willconflict and d" (tip)