Re: Killing bitkeeper 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 use BitKeeper to manage some binaries in a separate repository from 
our codebase.  To eliminate redundant disk space usage on our shared 
volumes and to make read-only "checkouts" fast for day-to-day usage, we 
just do a "bk export" instead of a "bk clone" for normal work.  We 
rarely  make changes to the binaries so this works fine.