Atomatic remote stacking ala Launchpad

Joke de Buhr joke.de.buhr at seiken.de
Wed Nov 25 12:51:03 GMT 2009


On Tuesday 24 November 2009 13:26:22 Matt Nordhoff wrote:
> Ivan Sagalaev wrote:
> > Hello!
> >
> > Robert Collins and Ian Clatworthy have explained to me a feature of
> > Launchpad where branches pushed there are not transmitted over the
> > network completely but magically created as stacked.
> >
> > I wonder if it's possible to do the same thing on our company's bzr
> > server.  For now we encourage people to create shared repos for their
> > projects and keep all branches within them. I'm not sure if it saves
> > only disk space on the server or also saves traffic when someone
> > pushes a local branch into a remote shared repo. If the branch is
> > still transmitted completely then that feature with remote stacking
> > can be a time-saver.
> 
> When pushing, only revisions not present in the target repo will be
> transmitted, whether it's normal, shared or stacked. When creating a
>  new branch, this means: If a shared is being used, well, just what I
>  said: it pushes revisions not present in the shared repo. If it's a
>  standalone branch, the new repo is obviously empty and you have to
>  push everything. If it's stacked, it pushes everything not present in
>  the stacked-on branch's repo.
> 
> The big benefit of stacking on a server is access control: if you use a
> shared repo, everybody needs write access to it, but with stacking,
>  they don't. If you don't need such fine-grained access control, it's
>  simpler to stick with shared repos.
> 
> If you're still interested, the feature Launchpad uses is called a
> stacking policy. I don't see any documentation, though...
> 

I read this thread and automatic server side stacking would be a nice 
feature for me. I'm currently using a smart server over http with apache 
authentication. Using stacking I could gain finer access control and 
reduce waste within the repository by deleting abandoned branches.

Any hint how I might activate such a stacking policy. I can't find 
anything within the documentation or stacked.txt. Searching the source 
code hasn't been productive so far.


Joke de Buhr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20091125/618cc09d/attachment.pgp 


More information about the bazaar mailing list