sapling/tests/test-merge2.out

0 files updated, 0 files merged, 0 files removed, 0 files unresolved
created new head
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
adding b
created new head
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
adding b
created new head
Make hg update more verbose by default (issue12) (including small changes to revert and backout to not show these stats with the exception of backout --merge) Show update stats (unless -q), e.g.: K files updated, L files merged, M files removed, N files unresolved Inform the user what to do after a merge: (branch merge, don't forget to commit) Inform the user what to do if a branch merge failed: There are unresolved merges, you can redo the full merge using: hg update -C X hg merge Y Inform the user what to do if a working directory merge failed: There are unresolved merges with locally modified files. 2006-05-02 20:44:02 +04:00			`0 files updated, 0 files merged, 0 files removed, 0 files unresolved`
warn about new heads on commit (issue842) 2008-03-21 13:06:02 +03:00			`created new head`
Make hg update more verbose by default (issue12) (including small changes to revert and backout to not show these stats with the exception of backout --merge) Show update stats (unless -q), e.g.: K files updated, L files merged, M files removed, N files unresolved Inform the user what to do after a merge: (branch merge, don't forget to commit) Inform the user what to do if a branch merge failed: There are unresolved merges, you can redo the full merge using: hg update -C X hg merge Y Inform the user what to do if a working directory merge failed: There are unresolved merges with locally modified files. 2006-05-02 20:44:02 +04:00			`0 files updated, 0 files merged, 0 files removed, 0 files unresolved`
Update tests to match new addremove chattiness. 2005-07-23 07:46:02 +04:00			`adding b`
warn about new heads on commit (issue842) 2008-03-21 13:06:02 +03:00			`created new head`
Make hg update more verbose by default (issue12) (including small changes to revert and backout to not show these stats with the exception of backout --merge) Show update stats (unless -q), e.g.: K files updated, L files merged, M files removed, N files unresolved Inform the user what to do after a merge: (branch merge, don't forget to commit) Inform the user what to do if a branch merge failed: There are unresolved merges, you can redo the full merge using: hg update -C X hg merge Y Inform the user what to do if a working directory merge failed: There are unresolved merges with locally modified files. 2006-05-02 20:44:02 +04:00			`0 files updated, 0 files merged, 0 files removed, 0 files unresolved`
Update tests to match new addremove chattiness. 2005-07-23 07:46:02 +04:00			`adding b`
warn about new heads on commit (issue842) 2008-03-21 13:06:02 +03:00			`created new head`