Playing with stacked branches

[Robert Collins]

On Thu, 2008-04-10 at 01:30 -0400, Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Robert Collins wrote:
> > On Tue, 2008-04-01 at 10:51 -0400, Aaron Bentley wrote:
> >> First, I thought we were going to use the term "stacked" rather than
> >> "shallow", but the current docs and parameters use "shallow".
> > 
> > Good point. I used shallow when I was thinking in UI terms. Perhaps
> > stacked would be better there too.
> 
> I think it would be a good idea, because the goal of stacking, efficient
> storage, isn't the same as the goal we've given for shallow branches.
> http://bazaar-vcs.org/HistoryHorizon
> 
> For shallow branching, the idea was that would be usable independently
> from their fallback repository, via a history horizon.

This is true. However the goal of stacking is not just efficient
storage, its less-than-complete downloads. Stacking doesn't imply
anything about size in and of itself, shallow does. Do we need two terms
perhaps? one for only some data downloaded, but remote access still
needed, and another for putting a horizon in place?

> >> The current implementation requires that the stacked-on branch be in a
> >> stacking-aware format.  Is that actually necessary?  Is it so that the
> >> branch can specify whether it is willing to be stacked on?
> > 
> > Its because the current implementation peeks under the hood to get at
> > the list of packs
> 
> Cool.  Since we're on the topic, do you think branches should be able to
> refuse to be stacked on?

I don't know; If stacking was always explicit I would say 'no'. But with
the policy work you've done it raises the chance of accidental stacking
occuring.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080411/5204cac7/attachment.pgp