[BUG] push to shared repo when lock is held

[Kent Gibson]

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



John Arbash Meinel wrote:
>
> This solves a lot of the problems we've had with launchpad, and I
> don't think it adds a lot of overhead. It does mean that we create
> a couple empty files (.bzr/branch/revision-history, for example)
> before we overwrite them during the copy stage. But I think it
> makes push creation *much* more stable.

Sounds good.
Do you think we might we still need a "--force" option?
The reason I ask is I was looking at bugs 30576, 45504 and 53340 and
was thinking that a "--force" option would provide a fallback that
would allow us to recover from all manner of failures.

>
> Honestly, I would prefer to deprecate creating branches with 'bzr
> push', and for that to be switched back to 'bzr branch'. But that
> doesn't seem to be the recognized workflow.

I only use "bzr push" to create branches on launchpad because that is
what the LP documentation says to do (https://code.launchpad.net/).
If you are going to deprecate it, that would be a good place to start.

Using branch requires you to specify the local and remote locations,
while push only requires the remote location (since it is called from
within the working tree), right?
In that case the average user might find the push to be more intuitive.


Cheers,
Kent.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFeYXDgoxTFTi1P8QRArIuAJ9VSie5B8ucqcsOp/Istg14Ay58OgCdHBvH
DhOnzZWLLCXdj15Q6Dzzx7E=
=7olX
-----END PGP SIGNATURE-----