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

Ancestors of 5

     2

4 2 0 

     3

Ancestors of 6 and 5

     4

4 3 2 1 0 

     5

Ancestors of 5 and 4

     6

4 2 0 

     7

Ancestors of 7, stop at 6

     8

6 

     9

Ancestors of 7, including revs

    10

7 6 5 4 3 2 1 0 

    11

Ancestors of 7, 5 and 3, including revs

    12

7 6 5 4 3 2 1 0 

    13

    14

Descendants of 5

    15

7 8 

    16

Descendants of 5 and 3

    17

6 7 8 

    18

Descendants of 5 and 4

    19

5 7 8