Next Steps for hpss, etc

[John Arbash Meinel]

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

On 11/22/2010 11:26 AM, Aaron Bentley wrote:
> On 11/18/2010 03:32 PM, John Arbash Meinel wrote:
>> 2) Shallow branching
>>    As defined by, creating a stacked local copy that has the data it
>>    needed to create the working copy, and no further policy. (It
>>    doesn't explicitly cache, but it doesn't avoid extra history, either)
> 
> How would this be different from stacked branching?
> 
> Do you imagine history horizons being implemented for this?
> 
> Aaron

Primarily the fact that stacked branching copies nothing during the
'branch' phase, but then goes back to the source branch to download
everything during the 'checkout' phase, but it then does not cache any
of that content. eg 'diff' still has to connect to the basis repo, and
download it gain.

History Horizons could interplay with this, but complicate it, as does
turning it into a cache-on-the-fly.

I'm proposing this mostly as something compatible but incrementally
better than what we have right now.

I don't try to worry about what to cache, since it uses the regular
stacking logic. (save things in this repo if they are not present in the
master repo.)

By not worrying about what to cache, I also don't worry about what *not*
to cache, which is more what History Horizon's is about.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzqsAoACgkQJdeBCYSNAAOKoQCfWXaBB4s8ej1gH6VL0WuOchQM
vKUAoKrOWooxo/1MC3wbsqpZo4NVP4hr
=gZ3B
-----END PGP SIGNATURE-----