This is an archive of the discontinued Mercurial Phabricator instance.

Differential D9173

tests: run test-copies-chain-merge.t also with copies in changesets
ClosedPublic

Authored by martinvonz on Oct 8 2020, 1:23 PM.

Details

Reviewers
pulkit
Group Reviewers
hg-reviewers
Commits
rHG5e72827dae1e: tests: run test-copies-chain-merge.t also with copies in changesets
Summary

We have these tests already and it seems like a waste to not run them
in the changesets case. The biggest differences stem from
hg log --follow not working with copies stored in the changeset
extras.

Diff Detail

Repository
rHG Mercurial
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

martinvonz created this revision.Oct 8 2020, 1:23 PM
martinvonz added a comment.Oct 9 2020, 10:57 AM

Reviewers: Up to here is ready for review (and uncontroversial, I would think)

pulkit accepted this revision.Oct 13 2020, 3:41 AM
This revision is now accepted and ready to land.Oct 13 2020, 3:41 AM
marmoute added a subscriber: marmoute.Oct 13 2020, 6:54 AM

This adds a non negligible amount of churn that conflict with an import bug series I submitted (See D9195 and above).

Can we drop it for now and restart review on a new diff? In particular, I do not understand why the changeset version of the algorithm is not giving use the same result as the compatibility one.

(cc @pulkit )

martinvonz added a comment.Oct 13 2020, 12:27 PM
In D9173#138208, @marmoute wrote:

This adds a non negligible amount of churn that conflict with an import bug series I submitted (See D9195 and above).
Can we drop it for now and restart review on a new diff?

That was sent for review after this series, so I don't think it's fair to drop this one for that reason.

In particular, I do not understand why the changeset version of the algorithm is not giving use the same result as the compatibility one.

I think I explained that in the commit message: hg log --follow <file> doesn't work with copy information (only) in the changelog, since it has a fast-path that follows the revisions in the filelog. We (probably I) will need to fix that some day...

marmoute added a comment.Oct 13 2020, 3:13 PM
In D9173#138235, @martinvonz wrote:
In D9173#138208, @marmoute wrote:

This adds a non negligible amount of churn that conflict with an import bug series I submitted (See D9195 and above).
Can we drop it for now and restart review on a new diff?

That was sent for review after this series, so I don't think it's fair to drop this one for that reason.

You probably noticed that I have been sending a pretty regular stream of patch on this topic over the last month. This series is just the continuation of this. I would have appreciated if you would have coordinated with me before starting sending arbitrary patch on this topic. The lack of communication is probably going to cost too many hours for both of us.

In particular, I do not understand why the changeset version of the algorithm is not giving use the same result as the compatibility one.

I think I explained that in the commit message: hg log --follow <file> doesn't work with copy information (only) in the changelog, since it has a fast-path that follows the revisions in the filelog. We (probably I) will need to fix that some day...

We should probably explicitly add this information around the if block.

pulkit added a comment.Oct 14 2020, 3:33 AM
In D9173#138239, @marmoute wrote:
In D9173#138235, @martinvonz wrote:
In D9173#138208, @marmoute wrote:

This adds a non negligible amount of churn that conflict with an import bug series I submitted (See D9195 and above).
Can we drop it for now and restart review on a new diff?

That was sent for review after this series, so I don't think it's fair to drop this one for that reason.

You probably noticed that I have been sending a pretty regular stream of patch on this topic over the last month. This series is just the continuation of this. I would have appreciated if you would have coordinated with me before starting sending arbitrary patch on this topic. The lack of communication is probably going to cost too many hours for both of us.

In particular, I do not understand why the changeset version of the algorithm is not giving use the same result as the compatibility one.

I think I explained that in the commit message: hg log --follow <file> doesn't work with copy information (only) in the changelog, since it has a fast-path that follows the revisions in the filelog. We (probably I) will need to fix that some day...

We should probably explicitly add this information around the if block.

Yes, it will be nice to get this documented around that block.

martinvonz added a comment.Oct 14 2020, 11:40 AM
In D9173#138276, @pulkit wrote:
In D9173#138239, @marmoute wrote:
In D9173#138235, @martinvonz wrote:
In D9173#138208, @marmoute wrote:

This adds a non negligible amount of churn that conflict with an import bug series I submitted (See D9195 and above).
Can we drop it for now and restart review on a new diff?

That was sent for review after this series, so I don't think it's fair to drop this one for that reason.

You probably noticed that I have been sending a pretty regular stream of patch on this topic over the last month. This series is just the continuation of this. I would have appreciated if you would have coordinated with me before starting sending arbitrary patch on this topic. The lack of communication is probably going to cost too many hours for both of us.

In particular, I do not understand why the changeset version of the algorithm is not giving use the same result as the compatibility one.

I think I explained that in the commit message: hg log --follow <file> doesn't work with copy information (only) in the changelog, since it has a fast-path that follows the revisions in the filelog. We (probably I) will need to fix that some day...

We should probably explicitly add this information around the if block.

Yes, it will be nice to get this documented around that block.

Agreed. I've sent D9204 for that.

Revision Contents
Changeset List

PathPackages
Mtests/test-copies-chain-merge.t (129 lines)

Diff 23182

tests/test-copies-chain-merge.t

#testcases filelog compatibility sidedata #testcases filelog compatibility changeset sidedata
===================================================== =====================================================
Test Copy tracing for chain of copies involving merge Test Copy tracing for chain of copies involving merge
===================================================== =====================================================
This test files covers copies/rename case for a chains of commit where merges 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 are involved. It cheks we do not have unwanted update of behavior and that the
different options to retrieve copies behave correctly. different options to retrieve copies behave correctly.
#if compatibility #if compatibility
$ cat >> $HGRCPATH << EOF $ cat >> $HGRCPATH << EOF
> [experimental] > [experimental]
> copies.read-from = compatibility > copies.read-from = compatibility
> EOF > EOF
#endif #endif
#if changeset
$ cat >> $HGRCPATH << EOF
> [experimental]
> copies.read-from = changeset-only
> copies.write-to = changeset-only
> EOF
#endif
#if sidedata #if sidedata
$ cat >> $HGRCPATH << EOF $ cat >> $HGRCPATH << EOF
> [format] > [format]
> exp-use-side-data = yes > exp-use-side-data = yes
> exp-use-copies-side-data-changeset = yes > exp-use-copies-side-data-changeset = yes
> EOF > EOF
#endif #endif
$ hg manifest --debug --rev 'desc("mBDm-0")' | grep '644 d' $ hg manifest --debug --rev 'desc("mBDm-0")' | grep '644 d'
b004912a8510032a0350a74daa2803dadfb00e12 644 d b004912a8510032a0350a74daa2803dadfb00e12 644 d
$ hg manifest --debug --rev 'desc("mDBm-0")' | grep '644 d' $ hg manifest --debug --rev 'desc("mDBm-0")' | grep '644 d'
b004912a8510032a0350a74daa2803dadfb00e12 644 d b004912a8510032a0350a74daa2803dadfb00e12 644 d
$ hg manifest --debug --rev 'desc("d-2")' | grep '644 d' $ hg manifest --debug --rev 'desc("d-2")' | grep '644 d'
b004912a8510032a0350a74daa2803dadfb00e12 644 d b004912a8510032a0350a74daa2803dadfb00e12 644 d
$ hg manifest --debug --rev 'desc("b-1")' | grep '644 d' $ hg manifest --debug --rev 'desc("b-1")' | grep '644 d'
169be882533bc917905d46c0c951aa9a1e288dcf 644 d 169be882533bc917905d46c0c951aa9a1e288dcf 644 d (no-changeset !)
b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 644 d (changeset !)
$ hg debugindex d $ hg debugindex d
rev linkrev nodeid p1 p2 rev linkrev nodeid p1 p2
0 2 169be882533b 000000000000 000000000000 0 2 169be882533b 000000000000 000000000000 (no-changeset !)
0 2 b789fdd96dc2 000000000000 000000000000 (changeset !)
1 8 b004912a8510 000000000000 000000000000 1 8 b004912a8510 000000000000 000000000000
Log output should not include a merge commit as it did not happen Log output should not include a merge commit as it did not happen
#if no-changeset
$ hg log -Gfr 'desc("mBDm-0")' d $ hg log -Gfr 'desc("mBDm-0")' d
o 8 d-2 re-add d o 8 d-2 re-add d
| |
~ ~
#else
$ hg log -Gfr 'desc("mBDm-0")' d
o 8 d-2 re-add d
|
~
#endif
#if no-changeset
$ hg log -Gfr 'desc("mDBm-0")' d $ hg log -Gfr 'desc("mDBm-0")' d
o 8 d-2 re-add d o 8 d-2 re-add d
| |
~ ~
#else
$ hg log -Gfr 'desc("mDBm-0")' d
o 8 d-2 re-add d
|
~
#endif
$ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBDm-0")' $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBDm-0")'
M b M b
A d A d
R a R a
$ hg status --copies --rev 'desc("i-0")' --rev 'desc("mDBm-0")' $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mDBm-0")'
M b M b
A d A d
o | 3 a-1: d -move-> e o | 3 a-1: d -move-> e
|/ |/
o 2 i-2: c -move-> d o 2 i-2: c -move-> d
| |
o 1 i-1: a -move-> c o 1 i-1: a -move-> c
| |
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
#if no-changeset
$ hg manifest --debug --rev 'desc("mAEm-0")' | grep '644 f' $ hg manifest --debug --rev 'desc("mAEm-0")' | grep '644 f'
c39c6083dad048d5138618a46f123e2f397f4f18 644 f c39c6083dad048d5138618a46f123e2f397f4f18 644 f
$ hg manifest --debug --rev 'desc("mEAm-0")' | grep '644 f' $ hg manifest --debug --rev 'desc("mEAm-0")' | grep '644 f'
a9a8bc3860c9d8fa5f2f7e6ea8d40498322737fd 644 f a9a8bc3860c9d8fa5f2f7e6ea8d40498322737fd 644 f
$ hg manifest --debug --rev 'desc("a-2")' | grep '644 f' $ hg manifest --debug --rev 'desc("a-2")' | grep '644 f'
263ea25e220aaeb7b9bac551c702037849aa75e8 644 f 263ea25e220aaeb7b9bac551c702037849aa75e8 644 f
$ hg manifest --debug --rev 'desc("e-2")' | grep '644 f' $ hg manifest --debug --rev 'desc("e-2")' | grep '644 f'
71b9b7e73d973572ade6dd765477fcee6890e8b1 644 f 71b9b7e73d973572ade6dd765477fcee6890e8b1 644 f
$ hg debugindex f $ hg debugindex f
rev linkrev nodeid p1 p2 rev linkrev nodeid p1 p2
0 4 263ea25e220a 000000000000 000000000000 0 4 263ea25e220a 000000000000 000000000000
1 10 71b9b7e73d97 000000000000 000000000000 1 10 71b9b7e73d97 000000000000 000000000000
2 19 c39c6083dad0 263ea25e220a 71b9b7e73d97 2 19 c39c6083dad0 263ea25e220a 71b9b7e73d97
3 20 a9a8bc3860c9 71b9b7e73d97 263ea25e220a 3 20 a9a8bc3860c9 71b9b7e73d97 263ea25e220a
#else
$ hg manifest --debug --rev 'desc("mAEm-0")' | grep '644 f'
498e8799f49f9da1ca06bb2d6d4accf165c5b572 644 f
$ hg manifest --debug --rev 'desc("mEAm-0")' | grep '644 f'
c5b506a7118667a38a9c9348a1f63b679e382f57 644 f
$ hg manifest --debug --rev 'desc("a-2")' | grep '644 f'
b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 644 f
$ hg manifest --debug --rev 'desc("e-2")' | grep '644 f'
1e88685f5ddec574a34c70af492f95b6debc8741 644 f
$ hg debugindex f
rev linkrev nodeid p1 p2
0 4 b789fdd96dc2 000000000000 000000000000
1 10 1e88685f5dde 000000000000 000000000000
2 19 498e8799f49f b789fdd96dc2 1e88685f5dde
3 20 c5b506a71186 1e88685f5dde b789fdd96dc2
#endif
# Here the filelog based implementation is not looking at the rename # Here the filelog based implementation is not looking at the rename
# information (because the file exist on both side). However the changelog # information (because the file exist on both side). However the changelog
# based on works fine. We have different output. # based on works fine. We have different output.
$ hg status --copies --rev 'desc("a-2")' --rev 'desc("mAEm-0")' $ hg status --copies --rev 'desc("a-2")' --rev 'desc("mAEm-0")'
M f M f
b (no-filelog !) b (no-filelog !)
2 files updated, 0 files merged, 1 files removed, 0 files unresolved 2 files updated, 0 files merged, 1 files removed, 0 files unresolved
$ hg mv h i $ hg mv h i
$ hg commit -m "f-1: rename h -> i" $ hg commit -m "f-1: rename h -> i"
created new head created new head
$ hg mv --force i d $ hg mv --force i d
$ hg commit -m "f-2: rename i -> d" $ hg commit -m "f-2: rename i -> d"
$ hg debugindex d $ hg debugindex d
rev linkrev nodeid p1 p2 rev linkrev nodeid p1 p2
0 2 169be882533b 000000000000 000000000000 0 2 169be882533b 000000000000 000000000000 (no-changeset !)
0 2 b789fdd96dc2 000000000000 000000000000 (changeset !)
1 8 b004912a8510 000000000000 000000000000 1 8 b004912a8510 000000000000 000000000000
2 22 4a067cf8965d 000000000000 000000000000 2 22 4a067cf8965d 000000000000 000000000000 (no-changeset !)
2 22 fe6f8b4f507f 000000000000 000000000000 (changeset !)
$ hg up 'desc("b-1")' $ hg up 'desc("b-1")'
3 files updated, 0 files merged, 0 files removed, 0 files unresolved 3 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg merge 'desc("f-2")' $ hg merge 'desc("f-2")'
1 files updated, 0 files merged, 1 files removed, 0 files unresolved 1 files updated, 0 files merged, 1 files removed, 0 files unresolved
(branch merge, don't forget to commit) (branch merge, don't forget to commit)
$ hg ci -m 'mBFm-0 simple merge - one way' $ hg ci -m 'mBFm-0 simple merge - one way'
$ hg up 'desc("f-2")' $ hg up 'desc("f-2")'
1 files updated, 0 files merged, 0 files removed, 0 files unresolved 1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg status --copies --rev 'desc("f-2")' --rev 'desc("mFBm-0")' $ hg status --copies --rev 'desc("f-2")' --rev 'desc("mFBm-0")'
M b M b
$ hg status --copies --rev 'desc("f-1")' --rev 'desc("mFBm-0")' $ hg status --copies --rev 'desc("f-1")' --rev 'desc("mFBm-0")'
M b M b
M d M d
i (no-filelog !) i (no-filelog !)
R i R i
#if no-changeset
$ hg log -Gfr 'desc("mBFm-0")' d $ hg log -Gfr 'desc("mBFm-0")' d
o 22 f-2: rename i -> d o 22 f-2: rename i -> d
| |
o 21 f-1: rename h -> i o 21 f-1: rename h -> i
: :
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
#else
$ hg log -Gfr 'desc("mBFm-0")' d
o 22 f-2: rename i -> d
|
~
#endif
#if no-changeset
$ hg log -Gfr 'desc("mFBm-0")' d $ hg log -Gfr 'desc("mFBm-0")' d
o 22 f-2: rename i -> d o 22 f-2: rename i -> d
| |
o 21 f-1: rename h -> i o 21 f-1: rename h -> i
: :
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
#else
$ hg log -Gfr 'desc("mFBm-0")' d
o 22 f-2: rename i -> d
|
~
#endif
Merge: Merge:
- one with change to a file - one with change to a file
- one deleting and recreating the file - one deleting and recreating the file
Unlike in the 'BD/DB' cases, an actual merge happened here. So we should Unlike in the 'BD/DB' cases, an actual merge happened here. So we should
consider history and rename on both branch of the merge. consider history and rename on both branch of the merge.
M d M d
$ hg status --copies --rev 'desc("d-2")' --rev 'desc("mGDm-0")' $ hg status --copies --rev 'desc("d-2")' --rev 'desc("mGDm-0")'
M d M d
$ hg status --copies --rev 'desc("g-1")' --rev 'desc("mDGm-0")' $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mDGm-0")'
M d M d
$ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGDm-0")' $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGDm-0")'
M d M d
#if no-changeset
$ hg log -Gfr 'desc("mDGm-0")' d $ hg log -Gfr 'desc("mDGm-0")' d
o 26 mDGm-0 simple merge - one way o 26 mDGm-0 simple merge - one way
|\ |\
| o 25 g-1: update d | o 25 g-1: update d
| | | |
o | 8 d-2 re-add d o | 8 d-2 re-add d
|/ |/
o 2 i-2: c -move-> d o 2 i-2: c -move-> d
| |
o 1 i-1: a -move-> c o 1 i-1: a -move-> c
| |
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
#else
$ hg log -Gfr 'desc("mDGm-0")' d
o 26 mDGm-0 simple merge - one way
|\
| o 25 g-1: update d
| |
o | 8 d-2 re-add d
|/
o 2 i-2: c -move-> d
|
~
#endif
#if no-changeset
$ hg log -Gfr 'desc("mDGm-0")' d $ hg log -Gfr 'desc("mDGm-0")' d
o 26 mDGm-0 simple merge - one way o 26 mDGm-0 simple merge - one way
|\ |\
| o 25 g-1: update d | o 25 g-1: update d
| | | |
o | 8 d-2 re-add d o | 8 d-2 re-add d
|/ |/
o 2 i-2: c -move-> d o 2 i-2: c -move-> d
| |
o 1 i-1: a -move-> c o 1 i-1: a -move-> c
| |
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
#else
$ hg log -Gfr 'desc("mDGm-0")' d
o 26 mDGm-0 simple merge - one way
|\
| o 25 g-1: update d
| |
o | 8 d-2 re-add d
|/
o 2 i-2: c -move-> d
|
~
#endif
Merge: Merge:
- one with change to a file (d) - one with change to a file (d)
- one overwriting that file with a rename (from h to i, to d) - one overwriting that file with a rename (from h to i, to d)
This case is similar to BF/FB, but an actual merge happens, so both side of the This case is similar to BF/FB, but an actual merge happens, so both side of the
history are relevant. history are relevant.
M d M d
h (no-filelog !) h (no-filelog !)
R h R h
$ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGFm-0")' $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGFm-0")'
M d M d
h (no-filelog !) h (no-filelog !)
R h R h
#if no-changeset
$ hg log -Gfr 'desc("mFGm-0")' d $ hg log -Gfr 'desc("mFGm-0")' d
o 28 mFGm-0 simple merge - one way o 28 mFGm-0 simple merge - one way
|\ |\
| o 25 g-1: update d | o 25 g-1: update d
| | | |
o | 22 f-2: rename i -> d o | 22 f-2: rename i -> d
| | | |
o | 21 f-1: rename h -> i o | 21 f-1: rename h -> i
|/ |/
o 2 i-2: c -move-> d o 2 i-2: c -move-> d
| |
o 1 i-1: a -move-> c o 1 i-1: a -move-> c
| |
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
#else
$ hg log -Gfr 'desc("mFGm-0")' d
o 28 mFGm-0 simple merge - one way
|\
| o 25 g-1: update d
| |
o | 22 f-2: rename i -> d
|/
o 2 i-2: c -move-> d
|
~
#endif
#if no-changeset
$ hg log -Gfr 'desc("mGFm-0")' d $ hg log -Gfr 'desc("mGFm-0")' d
@ 29 mGFm-0 simple merge - the other way @ 29 mGFm-0 simple merge - the other way
|\ |\
| o 25 g-1: update d | o 25 g-1: update d
| | | |
o | 22 f-2: rename i -> d o | 22 f-2: rename i -> d
| | | |
o | 21 f-1: rename h -> i o | 21 f-1: rename h -> i
|/ |/
o 2 i-2: c -move-> d o 2 i-2: c -move-> d
| |
o 1 i-1: a -move-> c o 1 i-1: a -move-> c
| |
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
#else
$ hg log -Gfr 'desc("mGFm-0")' d
@ 29 mGFm-0 simple merge - the other way
|\
| o 25 g-1: update d
| |
o | 22 f-2: rename i -> d
|/
o 2 i-2: c -move-> d
|
~
#endif
Comparing with merging with a deletion (and keeping the file) Comparing with merging with a deletion (and keeping the file)
------------------------------------------------------------- -------------------------------------------------------------
Merge: Merge:
- one removing a file (d) - one removing a file (d)
- one updating that file - one updating that file
| |
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
'a' is the copy source of 'd' 'a' is the copy source of 'd'
$ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCGm-0")' $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCGm-0")'
A d A d
a (no-compatibility !) a (no-compatibility no-changeset !)
R a R a
$ hg status --copies --rev 'desc("i-0")' --rev 'desc("mGCm-0")' $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mGCm-0")'
A d A d
a (no-compatibility !) a (no-compatibility no-changeset !)
R a R a
$ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCGm-0")' $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCGm-0")'
A d A d
$ hg status --copies --rev 'desc("c-1")' --rev 'desc("mGCm-0")' $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mGCm-0")'
A d A d
$ hg status --copies --rev 'desc("g-1")' --rev 'desc("mCGm-0")' $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mCGm-0")'
$ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGCm-0")' $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGCm-0")'
o 0 i-0 initial commit: a b h o 0 i-0 initial commit: a b h
'a' is the the copy source of 'd' 'a' is the the copy source of 'd'
$ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCB-revert-m-0")' $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCB-revert-m-0")'
M b M b
A d A d
a (no-compatibility !) a (no-compatibility no-changeset !)
R a R a
$ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBC-revert-m-0")' $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBC-revert-m-0")'
M b M b
A d A d
a (no-compatibility !) a (no-compatibility no-changeset !)
R a R a
$ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCB-revert-m-0")' $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCB-revert-m-0")'
M b M b
A d A d
$ hg status --copies --rev 'desc("c-1")' --rev 'desc("mBC-revert-m-0")' $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mBC-revert-m-0")'
M b M b
A d A d
$ hg status --copies --rev 'desc("b-1")' --rev 'desc("mCB-revert-m-0")' $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mCB-revert-m-0")'
requirements requirements
preserved: * (glob) preserved: * (glob)
added: exp-copies-sidedata-changeset, exp-sidedata-flag added: exp-copies-sidedata-changeset, exp-sidedata-flag
#endif #endif
#if no-compatibility #if no-compatibility no-changeset
$ for rev in `hg log --rev 'all()' -T '{rev}\n'`; do $ for rev in `hg log --rev 'all()' -T '{rev}\n'`; do
> echo "##### revision $rev #####" > echo "##### revision $rev #####"
> hg debugsidedata -c -v -- $rev > hg debugsidedata -c -v -- $rev
> hg debugchangedfiles $rev > hg debugchangedfiles $rev
> done > done
##### revision 0 ##### ##### revision 0 #####
1 sidedata entries 1 sidedata entries