bzr push one branch below another

[Colin D Bennett]

On Wed, 10 Aug 2011 08:53:23 +0100
Michael Gliwinski <Michael.Gliwinski at henderson-group.com> wrote:

> On Wednesday 10 Aug 2011 07:27:30 Andreas Ostermann wrote:
> > But what bazaar should avoid is to push into a shared repository
> > location.
> > 
> > I created a shared repository:
> > 
> > xxx/projectA
> > 
> > Then wen had some branches there:
> > 
> > xxx/projectA/userA
> > xxx/projectA/userB
> > xxx/projectA/userC
> > 
> > My colleague accidentaly pushed into xxx/projectA, which directly
> > created a branch there. I think this should be avoided.
> 
> Well, this is actually useful as well.  IIRC it's even mentioned in
> the user guide.  E.g. for some of our projects we have:
> 
>   .../projectA                   # trunk
>   .../projectA/feature1          # common feature branch
>   .../projectA/user1/feature1    # user1's feature branch

Agreed.  Please don't remove the ability to have a branch in the root
of a shared repository.

However, I think there is still a good solution to Andreas's
colleague's problem of accidentally pushing to xxx/projectA instead of
xxx/projectA/userB:  Add some way to specifically tell Bazaar not to
allow a branch to be created in a specific location.  Perhaps create
a .bzr/no-branches-allowed file?  Or an option in the repository config
file?

Regards,
Colin