#testcases filelog compatibility changeset sidedata upgraded

=====================================================

Test Copy tracing for chain of copies involving merge

=====================================================

This test files covers copies/rename case for a chains of commit where merges

are involved. It cheks we do not have unwanted update of behavior and that the

different options to retrieve copies behave correctly.

Setup

=====

use git diff to see rename

  $ cat << EOF >> $HGRCPATH

  > [diff]

  > git=yes

  > [command-templates]

  > log={rev} {desc}\n

  > EOF

#if compatibility

  $ cat >> $HGRCPATH << EOF

  > [experimental]

  > copies.read-from = compatibility

  > EOF

#endif

#if changeset

  $ cat >> $HGRCPATH << EOF

  > [experimental]

  > copies.read-from = changeset-only

  > copies.write-to = changeset-only

  > EOF

#endif

#if sidedata

  $ cat >> $HGRCPATH << EOF

  > [format]

  > exp-use-side-data = yes

  > exp-use-copies-side-data-changeset = yes

  > EOF

#endif

  $ cat > same-content.txt << EOF

  > Here is some content that will be the same accros multiple file.

  > 

  > This is done on purpose so that we end up in some merge situation, were the

  > resulting content is the same as in the parent(s), but a new filenodes still

  > need to be created to record some file history information (especially

  > about copies).

  > EOF

  $ hg init repo-chain

  $ cd repo-chain

Add some linear rename initialy

  $ cp ../same-content.txt a

  $ cp ../same-content.txt b

  $ cp ../same-content.txt h

  $ hg ci -Am 'i-0 initial commit: a b h'

  adding a

  adding b

  adding h

  $ hg mv a c

  $ hg ci -Am 'i-1: a -move-> c'

  $ hg mv c d

  $ hg ci -Am 'i-2: c -move-> d'

  $ hg log -G

  @  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

And having another branch with renames on the other side

  $ hg mv d e

  $ hg ci -Am 'a-1: d -move-> e'

  $ hg mv e f

  $ hg ci -Am 'a-2: e -move-> f'

  $ hg log -G --rev '::.'

  @  4 a-2: e -move-> f

  |

  o  3 a-1: d -move-> e

  |

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Have a branching with nothing on one side

  $ hg up 'desc("i-2")'

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

  $ echo foo > b

  $ hg ci -m 'b-1: b update'

  created new head

  $ hg log -G --rev '::.'

  @  5 b-1: b update

  |

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Create a branch that delete a file previous renamed

  $ hg up 'desc("i-2")'

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

  $ hg rm d

  $ hg ci -m 'c-1 delete d'

  created new head

  $ hg log -G --rev '::.'

  @  6 c-1 delete d

  |

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Create a branch that delete a file previous renamed and recreate it

  $ hg up 'desc("i-2")'

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

  $ hg rm d

  $ hg ci -m 'd-1 delete d'

  created new head

  $ echo bar > d

  $ hg add d

  $ hg ci -m 'd-2 re-add d'

  $ hg log -G --rev '::.'

  @  8 d-2 re-add d

  |

  o  7 d-1 delete d

  |

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Having another branch renaming a different file to the same filename as another

  $ hg up 'desc("i-2")'

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

  $ hg mv b g

  $ hg ci -m 'e-1 b -move-> g'

  created new head

  $ hg mv g f

  $ hg ci -m 'e-2 g -move-> f'

  $ hg log -G --rev '::.'

  @  10 e-2 g -move-> f

  |

  o  9 e-1 b -move-> g

  |

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Setup all merge

===============

This is done beforehand to validate that the upgrade process creates valid copy

information.

merging with unrelated change does not interfere with the renames

---------------------------------------------------------------

- rename on one side

- unrelated change on the other side

  $ case_desc="simple merge - A side: multiple renames, B side: unrelated update"

  $ hg up 'desc("b-1")'

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

  $ hg merge 'desc("a-2")'

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

  (branch merge, don't forget to commit)

  $ hg ci -m "mBAm-0 $case_desc - one way"

  $ hg up 'desc("a-2")'

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

  $ hg merge 'desc("b-1")'

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

  (branch merge, don't forget to commit)

  $ hg ci -m "mABm-0 $case_desc - the other way"

  created new head

  $ hg log -G --rev '::(desc("mABm")+desc("mBAm"))'

  @    12 mABm-0 simple merge - A side: multiple renames, B side: unrelated update - the other way

  |\

  +---o  11 mBAm-0 simple merge - A side: multiple renames, B side: unrelated update - one way

  | |/

  | o  5 b-1: b update

  | |

  o |  4 a-2: e -move-> f

  | |

  o |  3 a-1: d -move-> e

  |/

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

merging with the side having a delete

-------------------------------------

case summary:

- one with change to an unrelated file

- one deleting the change

and recreate an unrelated file after the merge

  $ case_desc="simple merge - C side: delete a file with copies history , B side: unrelated update"

  $ hg up 'desc("b-1")'

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

  $ hg merge 'desc("c-1")'

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

  (branch merge, don't forget to commit)

  $ hg ci -m "mBCm-0 $case_desc - one way"

  $ echo bar > d

  $ hg add d

  $ hg ci -m 'mBCm-1 re-add d'

  $ hg up 'desc("c-1")'

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

  $ hg merge 'desc("b-1")'

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

  (branch merge, don't forget to commit)

  $ hg ci -m "mCBm-0 $case_desc - the other way"

  created new head

  $ echo bar > d

  $ hg add d

  $ hg ci -m 'mCBm-1 re-add d'

  $ hg log -G --rev '::(desc("mCBm")+desc("mBCm"))'

  @  16 mCBm-1 re-add d

  |

  o    15 mCBm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - the other way

  |\

  | | o  14 mBCm-1 re-add d

  | | |

  +---o  13 mBCm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - one way

  | |/

  | o  6 c-1 delete d

  | |

  o |  5 b-1: b update

  |/

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Comparing with a merge re-adding the file afterward

---------------------------------------------------

Merge:

- one with change to an unrelated file

- one deleting and recreating the change

  $ case_desc="simple merge - B side: unrelated update, D side: delete and recreate a file (with different content)"

  $ hg up 'desc("b-1")'

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

  $ hg merge 'desc("d-2")'

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

  (branch merge, don't forget to commit)

  $ hg ci -m "mBDm-0 $case_desc - one way"

  $ hg up 'desc("d-2")'

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

  $ hg merge 'desc("b-1")'

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

  (branch merge, don't forget to commit)

  $ hg ci -m "mDBm-0 $case_desc - the other way"

  created new head

  $ hg log -G --rev '::(desc("mDBm")+desc("mBDm"))'

  @    18 mDBm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - the other way

  |\

  +---o  17 mBDm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - one way

  | |/

  | o  8 d-2 re-add d

  | |

  | o  7 d-1 delete d

  | |

  o |  5 b-1: b update

  |/

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Comparing with a merge with colliding rename

--------------------------------------------

Subcase: new copy information on both side

``````````````````````````````````````````

- the "e-" branch renaming b to f (through 'g')

- the "a-" branch renaming d to f (through e)

  $ case_desc="merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f)"

  $ hg up 'desc("a-2")'

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

  $ hg merge 'desc("e-2")'

  1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)

  (branch merge, don't forget to commit)

  $ hg ci -m "mAEm-0 $case_desc - one way"

  $ hg up 'desc("e-2")'

  2 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)

  $ hg merge 'desc("a-2")'

  1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)

  (branch merge, don't forget to commit)

  $ hg ci -m "mEAm-0 $case_desc - the other way"

  created new head

  $ hg log -G --rev '::(desc("mAEm")+desc("mEAm"))'

  @    20 mEAm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - the other way

  |\

  +---o  19 mAEm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - one way

  | |/

  | o  10 e-2 g -move-> f

  | |

  | o  9 e-1 b -move-> g

  | |

  o |  4 a-2: e -move-> f

  | |

  o |  3 a-1: d -move-> e

  |/

  o  2 i-2: c -move-> d

  |

  o  1 i-1: a -move-> c

  |

  o  0 i-0 initial commit: a b h

Subcase: existing copy information overwritten on one branch

````````````````````````````````````````````````````````````

Merge:

- one with change to an unrelated file (b)

- one overwriting a file (d) with a rename (from h to i to d)