RFC, poke at 'shallow' branches

[John Arbash Meinel]

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

I believe Collin Watson pointed out one of the unique features of the
UDD workflow. Specifically, that rather than making 100s of branches of
a given project, he makes 1-2 branches of 100s of projects. As such, he
isn't helped a lot by a shared repository, since it is generally always
going to be new data he has to download. So decreasing the data
downloaded for "give me something to work with" is quite useful for
improving his daily workflow.

It is something that our 'shallow' branch design could help. Here I'm
defining it as a stacked branch that has enough data locally to do work.

For the implementation, I was thinking that it wouldn't be too hard to
add a "get_shallow_stream()" to the StreamSource object, which would
fetch a revision and its contents without filtering out the basis
inventory. And at the UI level, it would be exposed as "bzr branch
- --shallow".

Just some thoughts,

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

iEYEARECAAYFAktq7dwACgkQJdeBCYSNAAOWLwCgo88x4EVv3qyi+FJuHSKfMTub
aA8An1VHnC9n/CKRMGq8ndd4rsFot2Kv
=U/co
-----END PGP SIGNATURE-----