upstream/mercurial-mirror Files · tests/test-merge-commit.t

copies: add config option for writing copy metadata to file and/or changset...

copies: add config option for writing copy metadata to file and/or changset This introduces a config option that lets you choose to write copy metadata to the changeset extras instead of to filelog. There's also an option to write it to both places. I imagine that may possibly be useful when transitioning an existing repo. The copy metadata is stored as two fields in extras: one for copies since p1 and one for copies since p2. I may need to add more information later in order to make copy tracing faster. Specifically, I'm thinking out recording which files were added or removed so that copies._chaincopies() doesn't have to look at the manifest for that. But that would just be an optimization and that can be added once we know if it's necessary. I have also considered saving space by using replacing the destination file path by an index into the "files" list, but that can also be changed later (but before the feature is ready to release). Differential Revision: https://phab.mercurial-scm.org/D6183

Gregory Szorc - - Load All Authors

File last commit:

r37301:d4e62df1 default


                r42317:0e41f40b

default

Download file

             test-merge-commit.t
        
                    185 lines
            
             | 5.1 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-merge-commit.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      Check that renames are correctly saved by a commit after a merge

      Test with the merge on 3 having the rename on the local parent

        $ hg init a

        $ cd a

        $ echo line1 > foo

        $ hg add foo

        $ hg ci -m '0: add foo'

        $ echo line2 >> foo

        $ hg ci -m '1: change foo'

        $ hg up -C 0

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

        $ hg mv foo bar

        $ rm bar

        $ echo line0 > bar

        $ echo line1 >> bar

        $ hg ci -m '2: mv foo bar; change bar'

        created new head

        $ hg merge 1

        merging bar and foo to bar

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

        (branch merge, don't forget to commit)

        $ cat bar

        line0

        line1

        line2

        $ hg ci -m '3: merge with local rename'

        $ hg debugindex bar

           rev linkrev nodeid       p1           p2

             0       2 d35118874825 000000000000 000000000000

             1       3 5345f5ab8abd 000000000000 d35118874825

        $ hg debugrename bar

        bar renamed from foo:9e25c27b87571a1edee5ae4dddee5687746cc8e2

        $ hg debugindex foo

           rev linkrev nodeid       p1           p2

             0       0 690b295714ae 000000000000 000000000000

             1       1 9e25c27b8757 690b295714ae 000000000000

      Revert the content change from rev 2:

        $ hg up -C 2

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

        $ rm bar

        $ echo line1 > bar

        $ hg ci -m '4: revert content change from rev 2'

        created new head

        $ hg log --template '{rev}:{node|short} {parents}\n'

        4:2263c1be0967 2:0f2ff26688b9 

        3:0555950ead28 2:0f2ff26688b9 1:5cd961e4045d 

        2:0f2ff26688b9 0:2665aaee66e9 

        1:5cd961e4045d 

        0:2665aaee66e9 

      This should use bar@rev2 as the ancestor:

        $ hg --debug merge 3

          searching for copies back to rev 1

        resolving manifests

         branchmerge: True, force: False, partial: False

         ancestor: 0f2ff26688b9, local: 2263c1be0967+, remote: 0555950ead28

         preserving bar for resolve of bar

        starting 4 threads for background file closing (?)

         bar: versions differ -> m (premerge)

        picked tool ':merge' for bar (binary False symlink False changedelete False)

        merging bar

        my bar@2263c1be0967+ other bar@0555950ead28 ancestor bar@0f2ff26688b9

         premerge successful

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

        (branch merge, don't forget to commit)

        $ cat bar

        line1

        line2

        $ hg ci -m '5: merge'

        $ hg debugindex bar

           rev linkrev nodeid       p1           p2

             0       2 d35118874825 000000000000 000000000000

             1       3 5345f5ab8abd 000000000000 d35118874825

             2       4 ff4b45017382 d35118874825 000000000000

             3       5 3701b4893544 ff4b45017382 5345f5ab8abd

      Same thing, but with the merge on 3 having the rename

      on the remote parent:

        $ cd ..

        $ hg clone -U -r 1 -r 2 a b

        adding changesets

        adding manifests

        adding file changes

        added 3 changesets with 3 changes to 2 files (+1 heads)

        new changesets 2665aaee66e9:0f2ff26688b9

        $ cd b

        $ hg up -C 1

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

        $ hg merge 2

        merging foo and bar to bar

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

        (branch merge, don't forget to commit)

        $ cat bar

        line0

        line1

        line2

        $ hg ci -m '3: merge with remote rename'

        $ hg debugindex bar

           rev linkrev nodeid       p1           p2

             0       2 d35118874825 000000000000 000000000000

             1       3 5345f5ab8abd 000000000000 d35118874825

        $ hg debugrename bar

        bar renamed from foo:9e25c27b87571a1edee5ae4dddee5687746cc8e2

        $ hg debugindex foo

           rev linkrev nodeid       p1           p2

             0       0 690b295714ae 000000000000 000000000000

             1       1 9e25c27b8757 690b295714ae 000000000000

      Revert the content change from rev 2:

        $ hg up -C 2

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

        $ rm bar

        $ echo line1 > bar

        $ hg ci -m '4: revert content change from rev 2'

        created new head

        $ hg log --template '{rev}:{node|short} {parents}\n'

        4:2263c1be0967 2:0f2ff26688b9 

        3:3ffa6b9e35f0 1:5cd961e4045d 2:0f2ff26688b9 

        2:0f2ff26688b9 0:2665aaee66e9 

        1:5cd961e4045d 

        0:2665aaee66e9 

      This should use bar@rev2 as the ancestor:

        $ hg --debug merge 3

          searching for copies back to rev 1

        resolving manifests

         branchmerge: True, force: False, partial: False

         ancestor: 0f2ff26688b9, local: 2263c1be0967+, remote: 3ffa6b9e35f0

         preserving bar for resolve of bar

        starting 4 threads for background file closing (?)

         bar: versions differ -> m (premerge)

        picked tool ':merge' for bar (binary False symlink False changedelete False)

        merging bar

        my bar@2263c1be0967+ other bar@3ffa6b9e35f0 ancestor bar@0f2ff26688b9

         premerge successful

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

        (branch merge, don't forget to commit)

        $ cat bar

        line1

        line2

        $ hg ci -m '5: merge'

        $ hg debugindex bar

           rev linkrev nodeid       p1           p2

             0       2 d35118874825 000000000000 000000000000

             1       3 5345f5ab8abd 000000000000 d35118874825

             2       4 ff4b45017382 d35118874825 000000000000

             3       5 3701b4893544 ff4b45017382 5345f5ab8abd

        $ cd ..

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				Check that renames are correctly saved by a commit after a merge

				Test with the merge on 3 having the rename on the local parent

				$ hg init a
				$ cd a

				$ echo line1 > foo
				$ hg add foo
				$ hg ci -m '0: add foo'

				$ echo line2 >> foo
				$ hg ci -m '1: change foo'

				$ hg up -C 0
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved

				$ hg mv foo bar
				$ rm bar
				$ echo line0 > bar
				$ echo line1 >> bar
				$ hg ci -m '2: mv foo bar; change bar'
				created new head

				$ hg merge 1
				merging bar and foo to bar
				0 files updated, 1 files merged, 0 files removed, 0 files unresolved
				(branch merge, don't forget to commit)

				$ cat bar
				line0
				line1
				line2

				$ hg ci -m '3: merge with local rename'

				$ hg debugindex bar
				rev linkrev nodeid p1 p2
				0 2 d35118874825 000000000000 000000000000
				1 3 5345f5ab8abd 000000000000 d35118874825

				$ hg debugrename bar
				bar renamed from foo:9e25c27b87571a1edee5ae4dddee5687746cc8e2

				$ hg debugindex foo
				rev linkrev nodeid p1 p2
				0 0 690b295714ae 000000000000 000000000000
				1 1 9e25c27b8757 690b295714ae 000000000000


				Revert the content change from rev 2:

				$ hg up -C 2
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved
				$ rm bar
				$ echo line1 > bar
				$ hg ci -m '4: revert content change from rev 2'
				created new head

				$ hg log --template '{rev}:{node\|short} {parents}\n'
				4:2263c1be0967 2:0f2ff26688b9
				3:0555950ead28 2:0f2ff26688b9 1:5cd961e4045d
				2:0f2ff26688b9 0:2665aaee66e9
				1:5cd961e4045d
				0:2665aaee66e9

				This should use bar@rev2 as the ancestor:

				$ hg --debug merge 3
				searching for copies back to rev 1
				resolving manifests
				branchmerge: True, force: False, partial: False
				ancestor: 0f2ff26688b9, local: 2263c1be0967+, remote: 0555950ead28
				preserving bar for resolve of bar
				starting 4 threads for background file closing (?)
				bar: versions differ -> m (premerge)
				picked tool ':merge' for bar (binary False symlink False changedelete False)
				merging bar
				my bar@2263c1be0967+ other bar@0555950ead28 ancestor bar@0f2ff26688b9
				premerge successful
				0 files updated, 1 files merged, 0 files removed, 0 files unresolved
				(branch merge, don't forget to commit)

				$ cat bar
				line1
				line2

				$ hg ci -m '5: merge'

				$ hg debugindex bar
				rev linkrev nodeid p1 p2
				0 2 d35118874825 000000000000 000000000000
				1 3 5345f5ab8abd 000000000000 d35118874825
				2 4 ff4b45017382 d35118874825 000000000000
				3 5 3701b4893544 ff4b45017382 5345f5ab8abd


				Same thing, but with the merge on 3 having the rename
				on the remote parent:

				$ cd ..
				$ hg clone -U -r 1 -r 2 a b
				adding changesets
				adding manifests
				adding file changes
				added 3 changesets with 3 changes to 2 files (+1 heads)
				new changesets 2665aaee66e9:0f2ff26688b9
				$ cd b

				$ hg up -C 1
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved

				$ hg merge 2
				merging foo and bar to bar
				0 files updated, 1 files merged, 0 files removed, 0 files unresolved
				(branch merge, don't forget to commit)

				$ cat bar
				line0
				line1
				line2

				$ hg ci -m '3: merge with remote rename'

				$ hg debugindex bar
				rev linkrev nodeid p1 p2
				0 2 d35118874825 000000000000 000000000000
				1 3 5345f5ab8abd 000000000000 d35118874825

				$ hg debugrename bar
				bar renamed from foo:9e25c27b87571a1edee5ae4dddee5687746cc8e2

				$ hg debugindex foo
				rev linkrev nodeid p1 p2
				0 0 690b295714ae 000000000000 000000000000
				1 1 9e25c27b8757 690b295714ae 000000000000


				Revert the content change from rev 2:

				$ hg up -C 2
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved
				$ rm bar
				$ echo line1 > bar
				$ hg ci -m '4: revert content change from rev 2'
				created new head

				$ hg log --template '{rev}:{node\|short} {parents}\n'
				4:2263c1be0967 2:0f2ff26688b9
				3:3ffa6b9e35f0 1:5cd961e4045d 2:0f2ff26688b9
				2:0f2ff26688b9 0:2665aaee66e9
				1:5cd961e4045d
				0:2665aaee66e9

				This should use bar@rev2 as the ancestor:

				$ hg --debug merge 3
				searching for copies back to rev 1
				resolving manifests
				branchmerge: True, force: False, partial: False
				ancestor: 0f2ff26688b9, local: 2263c1be0967+, remote: 3ffa6b9e35f0
				preserving bar for resolve of bar
				starting 4 threads for background file closing (?)
				bar: versions differ -> m (premerge)
				picked tool ':merge' for bar (binary False symlink False changedelete False)
				merging bar
				my bar@2263c1be0967+ other bar@3ffa6b9e35f0 ancestor bar@0f2ff26688b9
				premerge successful
				0 files updated, 1 files merged, 0 files removed, 0 files unresolved
				(branch merge, don't forget to commit)

				$ cat bar
				line1
				line2

				$ hg ci -m '5: merge'

				$ hg debugindex bar
				rev linkrev nodeid p1 p2
				0 2 d35118874825 000000000000 000000000000
				1 3 5345f5ab8abd 000000000000 d35118874825
				2 4 ff4b45017382 d35118874825 000000000000
				3 5 3701b4893544 ff4b45017382 5345f5ab8abd

				$ cd ..