Comment 2 for bug 406206

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

Vincent Ladeuil wrote:
> I'm not sure what upload should do there...(apart from not blowing up like this, that is).
> If bzr is available on the remote site, there is no point in using upload,
> https://edge.launchpad.net/bzr-push-and-update is far more appropriate (and works today),
> and 'bzr push' itself should populate the working tree (but I'm not sure the smart server does that today).
>
> upload is mostly targeted at remote sites where bzr can't be installed and will never be as smart
> as the two solutions above.

Well, there are people who would have bzr on the remote server, but want
to not upload the history to their http site. (So they don't have to
worry as much about disabling download of the history.)

That's about the only situation I can think of.

John
=:->

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

iEYEARECAAYFAkqelrYACgkQJdeBCYSNAAOIKwCgvD0UXDc64+vVRjU55xyhNhgI
oCYAn3ko7/80j8Rmso22d9mlSmnV6WEh
=N11G
-----END PGP SIGNATURE-----