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

  $ hg init

     2

  $ echo a > a

     3

  $ hg ci -Am t

     4

  adding a

     5

     6

  $ hg mv a b

     7

  $ hg ci -Am t1

     8

  $ hg debugrename b

     9

  b renamed from a:b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3

    10

    11

  $ hg mv b a

    12

  $ hg ci -Am t2

    13

  $ hg debugrename a

    14

  a renamed from b:37d9b5d994eab34eda9c16b195ace52c7b129980

    15

    16

  $ hg debugrename --rev 1 b

    17

  b renamed from a:b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3

    18