Re: Killing bitkeeper history

Brendan Heading wrote:
[...]
> Respectfully, what's the point in using a revision control system if you 
> keep deleting all the history ?
> 

Well, ideally we want to keep the history, its just that after
stacking changeset upon changeset of modified tarballs makes the
repo impossible to manage/use on a day-to-day basis.

We ofcourse would still need to branch off versions of this
repository for some projects and pull those results into an
integration repository etc etc just like our other repositories
(which are comrised of graphics skinsets, scripts and ofcourse the
codebase).

>>     - How can I conveniently pile changes from a stripped
>>       repository onto the "backup repo" ?
> 
> clone the repository and put it somewhere before doing csetprune, but to 
> me it seems like a waste of time.

Hmmm, I was kind of hoping I could pile the new changesets onto an
ever growing history of changesets; what you suggest would be like
a single "undo" item where I would want a complete undo stack.

All that aside; I agree that we may have used the wrong tool for that
particular task... its what we used to do with CVS (and that was
still a hassle for the same reasons)... if I can get away with not
addressing that issue and finding a clunky but usable permenent
solution; I'll be a happy man ;-D

Cheers,
                         -Tristan