[RFC] prohibit push to lightweight checkout

[John Arbash Meinel]

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

Alexander Belchenko wrote:
> Hi,
> 
> As I'm using colo plugin more and more, I'm getting more and more
> lightweight checkouts on different machines. Unfortunately due to design
> decision behind lightweight checkouts it's almost impossible to push
> from one machine to another if master branch of lightweight checkout is
> on the same machine where checkout resides. Even more if user have
> similar branch on his local machine then I suspect bzr will
> *incorrectly* open local branch instead of remote one.
> 
> Therefore I think any actions which required write access to lightweight
> checkout should be prohibited to avoid user confusion and undesirable
> effects of changing the branch behind user back.
> 
> Am I wrong? Why?
> 
> Alexander
> 
> 
> 

Just to mention that push is really designed around pushing to a branch,
and not a working tree.

I don't see that it should be expressly forbidden to push to a
lightweight checkout, though the recommendation would certainly be to
have you push to the branch itself.

I guess I'm okay with blocking it, since it is fairly likely to not do
what the user actually wants. But I wonder if we couldn't make it easier
for it to do what they want instead...

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvbCFsACgkQJdeBCYSNAAPj8QCfXdrZvTTLWUjiYPHAjiRRB8Yy
UbAAoMV0O1hd/XJlfAboEg1Lnas4yLzy
=o65/
-----END PGP SIGNATURE-----