Re: bzr: public_branch

[Bojan Nikolic <bojan@bnikolic.co.uk>]

Hi Glen,

Both of these concepts are related to the bzr send command, so it is
worth reading the help text for this.

The bzr send command basically creates a compact data set that describes
fully that the changes you have made as a developer. The submit branch
defines against what revision those changes should be measured. In other
words bzr send sends the changes you made in your branch as compared to
the submit branch.

In order to calculate those changes, bzr must analyse the submit
branch. Therefore it is most efficient for the submit branch to be
local. 

However, in order for others to make sense of your changes their bzr
must be able to access the branch against which the changes were
calculated. Therefore there must be a public branch with same
information as the submit branch. 

Allowing you to set separate submit and public branches allows you to
have the most efficient setup while others still can use the public
branch to interpret the changes you send.

Best,
Bojan


-- 
Bojan Nikolic          ||          http://www.bnikolic.co.uk