clone and sprout with a revision id parameter

[Aaron Bentley]

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

Jan Hudec wrote:
> On Wed, Feb 08, 2006 at 15:31:51 +1100, Robert Collins wrote:
> 
>>In bzr we allow branch -r revno LOCATION to make a new branch. It seems
>>undefined right now what happens if a revid is passed in that is not on
>>the source branches revision-history.
>>
>>I think it should change create a best-guess revision history and switch
>>to it. What do you all think?
> 
> 
> I thought revision-history is going to DIE. It should create revision
> history of first parents, for the time being.

Yes.  I think the problem is that everyone picked their own 'hard
thing', and no one decided to do the simple things.  We should at least
get pull --pivot implemented, so people can see what it would be like if
there was no revision history.

(And in fact, I think we'll want to have an ancestry cache, but a
non-authoritative one)

I'd also like to know how/if history horizons will work once there's no
revision-history.  IIRC, the original idea was to remove old entries
from the top of the list.

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

iD8DBQFD6fnE0F+nu1YWqI0RAlRiAJwIm2Yfk3rEcNExQougJ0gQIws9UACfRzqY
xN6hcrn8KY04s58zn0iuAZk=
=kwhI
-----END PGP SIGNATURE-----