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

[Aaron Bentley]

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

James Blackwell wrote:
| I'm kind of curious. What is the general opinion of moving the
| revision-history for branches in shared repositories from the branch to
| the shared repo?
|
| Benefits:
|
|  - Ability to audit a shared-repo and check for prunable revisions.

You can already do this.

|  - create a new checkout or standalone branch based upon the information
|    stored in revision-history

That doesn't sound like an observable feature to me.

|  - Would feel more similiar to CVS, SVN, Bazaar-1.x and Arch (!)

| Drawbacks:
|  - would require the definitition of additional UI
|  - A branch has to track what revision-history its associated with.

This is the main problem with this idea-- you still need a 1:1 mapping
of branches and revision histories, and I can't see why it's any help to
store the revision history separately.  Hell, a branch mostly *is* its
revision history.

Presumably, this would mean separating the revision-history from the
branch lock, and that can't be a good idea.

Oh, and revision-history should be replaced with a last-revision pointer
before we consider this, anyhow.

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

iD8DBQFEHkZa0F+nu1YWqI0RArxJAKCF4X8UymlN3TKcJptbbJxbED2KgACfcp+l
mIjyJfkoWFvEQ5nFc9MN9dc=
=M3OJ
-----END PGP SIGNATURE-----