Skip to content
Snippets Groups Projects
Commit a381618210d0 authored by Manuel Jacob's avatar Manuel Jacob
Browse files

tests: test that push doesn’t complain about unstable changesets if no changes

When there’re no outgoing changes, push doesn’t complain about unstable
changesets.

There is currently a bug (see issue6372) that causes that there is an abort on
push when the outgoing changes contain another changeset even if that is not
obsolete or unstable. A test case and fix for that is sent in the next patch.
parent 10f48720ef95
No related branches found
No related tags found
No related merge requests found
......@@ -627,6 +627,26 @@
abort: push includes orphan changeset: cda648ca50f5!
[255]
with --force it will work anyway
$ hg push ../tmpc/ --force
pushing to ../tmpc/
searching for changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 2 files
1 new obsolescence markers
1 new orphan changesets
if the orphan changeset is already on the server, pushing should work
$ hg push ../tmpc/
pushing to ../tmpc/
searching for changes
no changes found
[1]
Test that extinct changeset are properly detected
$ hg log -r 'extinct()'
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment