Mercurial > hg
view tests/test-default-push.out @ 8742:a964ab624385
merge: allow merging going backwards
New behavior is generally superior and more correct, except possibly
with regards to missing files. hg up . is now effectively a no-op,
which is probably the desired behavior for people expecting to move to
tip, but may surprise people who were expecting deleted files to
reappear.
case 1: update to .
a-w -> a-w
classic: ancestor a
missing recreated right?
rmed recreated WRONG
added forgotten WRONG
changed preserved RIGHT
conflicted can't happen
backward merge: ancestor a (NO EFFECT)
missing missing wrong?
rm'ed rm'ed RIGHT
added preserved RIGHT
changed preserved RIGHT
conflicted can't happen
case 2: update to ancestor of .
a-b-w -> b-w
\
a
classic: ancestor a
missing recreated right?
rmed recreated wrong?
added forgotten wrong?
changed preserved RIGHT
conflicted preserved wrong?
backwards merge: ancestor b
missing missing or conflict right?
rm'ed missing or conflict right?
changed preserved RIGHT
conflicted merge RIGHT
added preserved right?
author | Matt Mackall <mpm@selenic.com> |
---|---|
date | Mon, 08 Jun 2009 18:14:44 -0500 |
parents | 0750f11152fe |
children | a3d73b3e1f8a |
line wrap: on
line source
adding a updating working directory 1 files updated, 0 files merged, 0 files removed, 0 files unresolved updating working directory 1 files updated, 0 files merged, 0 files removed, 0 files unresolved % push should push to default when default-push not set pushing searching for changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files % push should push to default-push when set pushing searching for changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files