[RFC] move revision-history from branch to shared repo

Aaron Bentley aaron.bentley at utoronto.ca
Mon Mar 20 13:00:45 GMT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Blackwell wrote:

|>That doesn't sound like an observable feature to me.
|
|
| branches associated with shared repos seem to have a file named
| branch-history in .bzr/branch. The lines in this file look like revision
| ids to me. This leaves me thinking that if this file were given a nice
| name like branch-history.bzr.dev then I could:
|
|  1. remove my bzr.dev branch with its working tree.
|  2. Later decide I want bzr.dev back
|  3. do something approximately equivilant "bzr branch --stored bzr.dev"
|     and rebuild the bzr.dev branch.

After giving this some more thought, you don't need any new fundamentals
to do this kind of thing.  Instead of keeping the revision-history
somewhere else, you keep the entire branch somewhere else.  Say, in
.branches in the repository root.  So you have both branches and
checkouts in your repository, in different places.  The checkouts can,
of course, be zapped at any time.  So it would be

1. rm -rf myrepo/bzr.dev
2. echo "oops"
3. bzr checkout --lightweight myrepo/.branches/bzr.dev myrepo/bzr.dev

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEHqd90F+nu1YWqI0RArKiAJ9oQvLM9jFrmemrpRI9cPZ2x1tABACeIduV
JjlHdW02W8+RBPlr0/wcjZQ=
=Qbqh
-----END PGP SIGNATURE-----




More information about the bazaar mailing list