Skip to content
  • Manuel Jacob's avatar
    absorb: preserve changesets which were already empty · 1ca0047fd7e1
    Manuel Jacob authored
    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.
    1ca0047fd7e1