.hg directory has eclipsed 3GB - how to deal with huge manifest?

[Paul R]

Michael> How about Concatenating changesets?

This would work to concatenate "the last N changesets".

I think the OP would much prefer to concatenate "the first
N changesets".

In many cases, it is derirable to concatenate changesets that are in the
middle of the history. For exemple you check-in a bug blob in revision
R5, then commit some work in R6, then realise your mistake with the blob
and checkin its removal in R7.

One may want to swap R6 and R7 so that the blob operations are linear
and sequentials in the history, then concatenate R5 and R6 to result in
a single R5 changeset doing nothing. The blob is no longer in the
history.

Problems are :

 1. changesets IDs are incrementals and could not be preserved

      This could maybe be adressed inserting a dummy changeset after the
      concatenation with the exact same id as the last changeset being
      concatenated. That would require to have a special kind of
      changeset designed to fix a concatenation of the history.

 2. if repository have been cloned, that would require a special kind of
    full-pulling that would checkfor such operation in the history.

For current solutions, see 

    http://www.selenic.com/mercurial/wiki/index.cgi/EditingHistory

      
-- 
  Paul