Re: Killing bitkeeper history

Tristan Van Berkom wrote:

> What I'd like to do; to make it a little more practicle; is
> to have a front-end repository that contains next to no history;
> so that we can easily check out packages (as tarballs); modify
> them and commit them; and every once and a while; completely
> trash the history and; if possible; throw that history onto some
> stack that we will never really need to touch unless something
> goes terribly wrong ;-)

Tristan,

Respectfully, what's the point in using a revision control system if you 
keep deleting all the history ?

There's a couple of better ways :

- use a filesystem and just keep the stuff there.
- spend a few days writing a web-based front end to a MySQL database, 
that allows you to upload and keep your datafiles there. It will be a 
lot more easier to handle than an SCM
- use one of the commercial document management products.

> To put the question(s) in a one-liner form:
>     - How can I remove all history from a repository ?

bk csetprune does this. But before going down this route, consider why 
you're using an SCM in the first place for this task if you want to 
discard the history.

>     - 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.

Brendan