- Given that the place you push the branch to (its "push location") might be different from the place that others get the branch from, branch's have public locations.
- Any tool that shares your branch with others (e.g. bzr send, a commit notifier or even lp-open) needs to have a public location to share with the world.
Hacking, Software Collaboration, Testing and Diverse Other Topics of General Interest to the Practicing Programmer
Thursday, February 26, 2009
Why you should have a public location for your branch
I asked this self-same question on the Bazaar mailing list the other day. Here's the answer:
Subscribe to:
Post Comments (Atom)
Blog Archive
-
►
2010
(68)
-
►
November
(14)
- testtools manuals
- Tests that print stuff
- Boiling kettles, unit tests and data
- Big or small?
- "Don't Make Me Think", thoughts for Launchpad
- Reviewing specs, rock on!
- Having an extra feature never hurts, rebutted
- And then what?
- Make it really easy to fix bugs on Ubuntu
- What else have you got?
- Ubuntu in a VM on OS X?
- Still going
- What to do, what to do
- Launchpad and UDS-N
-
►
November
(14)
-
▼
2009
(56)
-
▼
February
(16)
- Fourteen Monthses
- Why you should have a public location for your bra...
- Betterer Cloud
- Useful, unpolished Bazaar plugin
- 100% Pure Doing
- Server reinstalled
- One bird, two stones
- Scheduled Unreliability
- Neat trick
- Things every project needs
- Everything I ever learned about programming...
- Better Cloud
- Make your code testable
- Bazaar commands
- Having said that, let me say this...
- Launchpad and Bazaar in South America
-
▼
February
(16)

0 comments:
Post a Comment