Add --no-tree to bzr push

[ThomasRutter]

When pushing to a new location with the file: protocol, sometimes it may be desirable not to create a working tree at the new location, such as when disk space is premium or when you are pushing to a network share with relatively high latency.

There is no --no-tree option for push yet, so the workaround is to wait for the working tree to be created then do a bzr remove-tree, which can be slow.

[Martin Pool (mbp)]

That would be useful, also for init.

As a workaround, commit, remove-tree, then push.

[John A Meinel (jameinel)]

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

Martin Pool wrote:
> That would be useful, also for init.
>
> As a workaround, commit, remove-tree, then push.
>
> ** Changed in: bzr
> Status: New => Confirmed
>
> ** Changed in: bzr
> Importance: Undecided => Medium
>

Or "bzr branch . $OTHER --no-tree"

John
=:->

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

iEYEARECAAYFAktN4UgACgkQJdeBCYSNAANc4QCg0V4/lrImOyQEMUPVwpSttZRf
AcEAoIgqSBTAMkldyKj8uCvQ1y/11fuE
=8khs
-----END PGP SIGNATURE-----

[Matthew Gordon (mgordon)]

Added --no-tree option to push and init.