"Stripping" changesets from the past of a repository

Fabrizio Giudici fabrizio.giudici at tidalwave.it
Mon Nov 16 06:25:37 CST 2009


Hi all. A few months ago I've converted almost all of my projects that were
previously using Subversion to Mercurial and I'm pretty fine. A residual
problem is that my Mercurial repos are much larger than they should be as in
Subversion there were lots of binary files committed. I'd like to get rid of
every trace of those files, if possible:

1. Either by stripping a specific set of resources from a given revision
**backwards**
2. Or eventually scratching all revisions before a given one "R", so that it
seems that the repository has been created at revision "R".

I'm using the "strip" term, but of course the strip command is not the
solution, since it strips from a given point to the future.

In the former case, of course, I'm aware that the operation would mean to be
unable to recreate a build previously the given revision; in any case I'll
keep a copy of the current repositories for "historic" purposes. But
jettisoning several dozens (and possibly hundreds) megabytes of stuff that
now is no more needed would make it possible to clone my projects much more
easily than today.
-- 
View this message in context: http://old.nabble.com/%22Stripping%22-changesets-from-the-past-of-a-repository-tp26370998p26370998.html
Sent from the Mercurial mailing list archive at Nabble.com.



More information about the Mercurial mailing list