view tests/test-churn.out @ 9815:49efeed49c94

rebase: make sure the newancestor is used during the whole update (issue1561) Before this change, newancestor was used only once as a replacement for ancestor.ancestor, but merge.update calls ancestor.ancestor several times, so it ends up with the "wrong" ancestor (the real ancestor, but we want the parent of the rebased changeset for all but the first rebased changeset). Added a new test case for this: test-rebase-newancestor. Also, in one scenario in test-rebase-collapse, there was a spurious conflict caused by the same issue, so that test case was fixed by removing the now unneeded conflict resolution and the output was adapted accordingly.
author Christian Boos <cboos@bct-technology.com>
date Mon, 09 Nov 2009 20:15:49 +0100
parents 7d56b6ffef72
children 717c35d55fb3
line wrap: on
line source

% create test repository
adding a
adding b
adding c
% churn separate directories
user1      1 ***************************************************************
% churn all
user3      3 ***************************************************************
user1      3 ***************************************************************
user2      2 ******************************************
% churn up to rev 2
user2      2 ***************************************************************
user1      1 ********************************
% churn with aliases
alias3      3 **************************************************************
alias1      3 **************************************************************
user2       2 *****************************************
% churn with .hgchurn
alias3      3 **************************************************************
alias1      3 **************************************************************
user2       2 *****************************************
% churn with column specifier
user3      3 ***********************
user1      3 ***********************
user2      2 ***************
% churn by hour
06      1 *****************
09      2 *********************************
12      4 ******************************************************************
13      1 *****************
% churn with separated added/removed lines
user1           +3/-1 +++++++++++++++++++++++++++++++++++++++++--------------
user3           +3/-0 +++++++++++++++++++++++++++++++++++++++++
user2           +2/-0 +++++++++++++++++++++++++++
% changeset number churn
user1      4 ***************************************************************
user3      3 ***********************************************
user2      2 ********************************
adding foo
test      0