absorb: preserve changesets which were already empty Most commands in Mercurial (commit, rebase, absorb itself) don’t create empty changesets or drop them if they become empty. If there’s a changeset that’s empty, it must be a deliberate choice of the user. At least it shouldn’t be absorb’s responsibility to prune them. The fact that changesets that became empty during absorb are pruned, is unaffected by this. This case was found while writing patches which make it possible to configure absorb and rebase to not drop empty changesets. Even without having such config set, I think it’s valuable to preserve changesets which were already empty.

     1

#require no-windows

     2

     3

  $ . "$TESTDIR/remotefilelog-library.sh"

     4

     5

  $ cat >> $HGRCPATH <<EOF

     6

  > [extensions]

     7

  > remotefilelog=

     8

  > share=

     9

  > EOF

    10

    11

  $ hg init master

    12

  $ cd master

    13

  $ cat >> .hg/hgrc <<EOF

    14

  > [remotefilelog]

    15

  > server=True

    16

  > EOF

    17

  $ echo x > x

    18

  $ hg commit -qAm x

    19

    20

  $ cd ..

    21

    22

    23

  $ hgcloneshallow ssh://user@dummy/master source --noupdate -q

    24

  $ hg share source dest

    25

  updating working directory

    26

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

    27

  $ hg -R dest unshare