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

     2

== Local

     3

Ready.

     4

Un and Deux

     5

Eins und Zwei

     6

One and Two

     7

Eins und Zwei

     8

Uno und Due

     9

    10

== Remote

    11

Ready.

    12

REQ: foo?one=Vo&two=Efvy

    13

  -> Vo!boe!Efvy

    14

Un and Deux

    15

REQ: bar?b=Fjot&a=[xfj

    16

  -> Fjot!voe![xfj

    17

Eins und Zwei

    18

REQ: batch?cmds=foo:one=Pof,two=Uxp;bar:b=Fjot,a=[xfj;bar:b=Vop,a=Evf

    19

  -> Pof!boe!Uxp;Fjot!voe![xfj;Vop!voe!Evf

    20

One and Two

    21

Eins und Zwei

    22

Uno und Due