Sharing Branches

Asked by Hal

I am having trouble creating a branch from an existing repository, that I can be shared among other users. I can create the branch, and work with it fine, and merge changes. But other users cannot "see" this branch. Its purely private to me (or so it seems). I either am missing a step or don't have the correct syntax. I am using this example:

$ bzr init-repo --trees tmp
$ cd tmp
$ bzr branch http://bzr-project.example.com/foo.stable/ current
$ bzr branch current bugfix

This scenario "works" as long as I am the only one needing to access "bugfix" branch. What am I missing?

Question information

Language:
English Edit question
Status:
Answered
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
John A Meinel (jameinel) said :
#1

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

On 6/6/2012 7:15 PM, Hal wrote:
> New question #199610 on Bazaar:
> https://answers.launchpad.net/bzr/+question/199610
>
> I am having trouble creating a branch from an existing repository,
> that I can be shared among other users. I can create the branch,
> and work with it fine, and merge changes. But other users cannot
> "see" this branch. Its purely private to me (or so it seems). I
> either am missing a step or don't have the correct syntax. I am
> using this example:
>
> $ bzr init-repo --trees tmp $ cd tmp $ bzr branch
> http://bzr-project.example.com/foo.stable/ current $ bzr branch
> current bugfix
>
> This scenario "works" as long as I am the only one needing to
> access "bugfix" branch. What am I missing?
>

Bugfix the branch only exists on your local machine. You need to 'bzr
push' it to a shared location for other people to see it.

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

iEYEARECAAYFAk/PtioACgkQJdeBCYSNAAOCqgCg0DTzMbvcgo0lvmTv0cHnPd3G
oZYAnAwYxSXPPYW47m/5sqhNWEc6HGR/
=w6aT
-----END PGP SIGNATURE-----

Revision history for this message
Hal (hal-foobox) said :
#2

Thanks. But I guess that is getting into another problem as I get a completely different error now (nothing to do with original issue).

Can you help with this problem?

Provide an answer of your own, or ask Hal for more information if necessary.

To post a message you must log in.