Stefan Reichör <[EMAIL PROTECTED]> writes: > I played a bit with uncommit also. It seems that the uncommited > revision is kept in the repository. There should be a way to compact > the repository to delete unneeded revisions - or uncommit should do that.
True. In bzr, you have roughly 3 concepts : the working tree, the branch, and the repository. The repository is a DAG of revisions, that have been committed "somewhere by someone". This includes all your commits, and all their ancestors (i.e all the merges, ...). The branch is just one fully ordered set of revisions (the ones you see in "bzr log"). Sometimes, some revisions are kept in your repository while they are unrelated from your branch. This happens at least * When you uncommit * When you diff -r branch:somewhere/else (the nice thing with this is that the second diff will be faster, and a merge on the same branch will also be faster.So, in most cases, keeping the revision in the repository is the right thing to do). It would be cool to have a kind of garbage collector for revisions, but that wouldn't be easy to implement. The storage format is meant to be append-only, which is not compatible with the idea of deletion. It doesn't seem to be the priority as of now. A solution is to create a fresh branch with "bzr branch", which should only grab the usefull revisions. -- Matthieu _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
