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

     1

#require serve repobundlerepo

     2

     3

  $ hg init server

     4

  $ cd server

     5

  $ cat >> .hg/hgrc << EOF

     6

  > [extensions]

     7

  > strip=

     8

  > EOF

     9

    10

  $ echo 1 > foo

    11

  $ hg commit -A -m 'first'

    12

  adding foo

    13

  $ echo 2 > bar

    14

  $ hg commit -A -m 'second'

    15

  adding bar

    16

    17

Produce a bundle to use

    18

    19

  $ hg strip -r 1

    20

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

    21

  saved backup bundle to $TESTTMP/server/.hg/strip-backup/ed602e697e0f-cc9fff6a-backup.hg

    22

    23

Serve from a bundle file

    24

    25

  $ hg serve -R .hg/strip-backup/ed602e697e0f-cc9fff6a-backup.hg -d -p $HGPORT --pid-file=hg.pid

    26

  $ cat hg.pid >> $DAEMON_PIDS

    27

    28

Ensure we're serving from the bundle

    29

    30

  $ (get-with-headers.py localhost:$HGPORT 'file/tip/?style=raw')

    31

  200 Script output follows

    32

    33

    34

  -rw-r--r-- 2 bar

    35

  -rw-r--r-- 2 foo

    36

    37