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 execbit

     2

     3

  $ hg init

     4

  $ echo a > a

     5

  $ hg ci -Am'not executable'

     6

  adding a

     7

     8

  $ chmod +x a

     9

  $ hg ci -m'executable'

    10

  $ hg id

    11

  79abf14474dc tip

    12

    13

Make sure we notice the change of mode if the cached size == -1:

    14

    15

  $ hg rm a

    16

  $ hg revert -r 0 a

    17

  $ hg debugstate

    18

  n   0         -1 unset               a

    19

  $ hg status

    20

  M a

    21

    22

  $ hg up 0

    23

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

    24

  $ hg id

    25

  d69afc33ff8a

    26

  $ test -x a && echo executable -- bad || echo not executable -- good

    27

  not executable -- good

    28