view tests/test-backwards-remove.t @ 44720:601ce5392cb0

phabricator: restack any new orphans created by phabsend (issue6045)

Previously, posting a new review for a non head commit would orphan the head.
The general case is any descendant of the selected revisions got orphaned if
this was the first time the selected revisions were submitted.  It doesn't
happen when resubmitting.  I've already had coworkers hit this a few times and
get confused.  Since posting a review isn't generally thought of as an editing
operation, it would probably be easier for new users if we just restacked.

This avoids restacking existing orphans around the submission because that may
involve merge conflict resolution.  Users who already have orphans should know
how to stabilize them anyway.

Differential Revision: https://phab.mercurial-scm.org/D8438

  $ hg init
  $ echo This is file a1 > a
  $ hg add a
  $ hg commit -m "commit #0"
  $ ls
  a
  $ echo This is file b1 > b
  $ hg add b
  $ hg commit -m "commit #1"
  $ hg co 0
  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

B should disappear

  $ ls
  a