Pithy answer to "Why set a public branch?"

[Jonathan Lange]

On Sun, Feb 22, 2009 at 11:10 AM, Robert Collins
<robertc at robertcollins.net> wrote:
> On Sat, 2009-02-21 at 23:54 +0100, Jelmer Vernooij wrote:
>> On Sun, 2009-02-22 at 09:43 +1100, Robert Collins wrote:
>> > A public branch setting tells bzr where a branch is published. sending a
>> > bundle, making email notifications, lp-open - pretty much anything where
>> > you want to tell someone else where the branch is uses this.
>> >
>> > If its not set explicitly, I think it defaults to the push_location, or
>> > perhaps it doesn't but should.
>> I don't think the push_location is a good default for the
>> public_location. The push_location is usually a bzr+ssh:// or sftp://
>> URL, and that's usually not available by the rest of the world.
>
> I think it depends on the url.
> svn:// urls are usually world usable [perhaps requiring auth, but the
> same url], as are http://, and lp:. bzr+ssh://host/~/ urls are not world
> usable, nor are sftp://host/~/ urls. sftp://host/abspath *may be*.
> bzr://host/ probably are.

It also depends on the project. For a proprietary project, bzr+ssh://
is as public as a branch URL is going to get.

jml