shared storage and branch api

[Aaron Bentley]

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

Robert Collins wrote:
> On Tue, 2005-09-06 at 08:58 -0400, Aaron Bentley wrote:
> 
> 
>>So since the guarantees you thought were there about stores were never
>>there, I don't think they'll cause a problem when we move to supporting
>>shared storage.
> 
> 
> Ok, thats good. I think it might be a good idea to have the branch
> get_revision and so on actively filter for revisions-that-have been
> merged, (so that one can use the store to get any revision, and the
> branch to get relevant revisions).
> 
> What do you think?

I think that would be a loss.

There's only one circumstance I'm aware of in which it's useful for
get_revision to fail.  That's when we want to find out whether we need
to copy the revision into local storage.  Forcing get_revision to fail
when the data was already in local storage would cause us to download
and attempt to add things to the local stores that were already there.

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

iD8DBQFDHaQb0F+nu1YWqI0RAi5BAKCJ4frbNOuAZwkd3zx4pnmTWbKnrwCfac5s
44nPPQqzSJ4k1bv3J0MQNcI=
=ASG/
-----END PGP SIGNATURE-----