[MERGE] Set default push location to the parent branch

[Dmitry Vasiliev]

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

Andrew Bennetts wrote:
| Still, if this is a common workflow for you, it'd be good to find a
way to make
| it easier for you without compromising the common “make lots of feature
| branches” approach.  Perhaps we could teach "bzr push" to recognise some
| revisionspecs, so that you could do "bzr push submit:".  Or provide a
way for
| you to configure your locations.conf so that like for me, it
automatically does
| what you want most of the time.

I like the idea. With 'bzr push submit:' you don't need to do 'bzr info'
to refresh the parent's URL. However 'revision' term is a little
misconceptional for 'push'. What do you think about some abstract
protocol which operates on known URLs namespace? For example:

$ bzr push known://parent
$ bzr diff known://push

Also in this case some additional locations can be defined through
configuration:

$ bzr push known://branch1
$ bzr merge known://branch2
$ bzr pull known://mybranch

- --
Dmitry Vasiliev (dima at hlabs.spb.ru)
~  http://hlabs.spb.ru
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHrBXAQgKQGbus+5wRAvCxAJ9qW6d2ZzMmhu9VfIrKlCjrCgA6sQCdFMnU
sAWFlRzGCXl+mCGXwU383mE=
=FHBl
-----END PGP SIGNATURE-----