[MERGE] make 'push' default to parent branch

[Scott Scriven]

* Robert Collins <robertc at robertcollins.net> wrote:
> I'm curious, if they've just migrated from a centralised 
> system, why the user wouldn't use bzr's centralised workflow - 
> 'checkout', 'update' and 'commit' ?

That's a good point.

I'm assuming the user doesn't know about all the options bzr 
provides, and they may not be using an optimal approach.

Former cvs/svn users aren't as likely to run into 'push' issues 
because it's an alien concept.  Former git/hg/bitkeeper users may 
think they can just s/hg/bzr/ and expect everything to work.  
And, for most of the basics, they can.

I see these being the two approaches most likely to benefit from 
a default URL:

  / % bzr branch lp:foo
  /foo/ % hack hack hack
  /foo/ % bzr commit -m 'new feature'
  /foo/ % bzr push

  / % bzr branch lp:foo trunk
  / % bzr branch trunk feature
  /feature/ % hack hack hack
  /feature/ % bzr commit -m 'new feature'
  /trunk/ % bzr merge ../feature
  /trunk/ % bzr commit -m 'merged feature'
  /trunk/ % bzr push

Lone developers and small teams are most likely to work this way, 
since bigger teams probably need a gatekeeper.


-- Scott