Alexander Belchenko wrote:
> 2) but second part of the bug is that in many operations (pull, merge, missing), when I provide branch location in the command line, bzr anyway try to read parent_location from config, even if it's not used. Is it good?
We automatically set the parent location to the user-supplied location
when the parent location is not already set. So we must determine
whether the parent location is already set, even when the user supplies
a location.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Belchenko wrote:
> 2) but second part of the bug is that in many operations (pull, merge, missing), when I provide branch location in the command line, bzr anyway try to read parent_location from config, even if it's not used. Is it good?
We automatically set the parent location to the user-supplied location
when the parent location is not already set. So we must determine
whether the parent location is already set, even when the user supplies
a location.
Aaron
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org
nu1YWqI0RAsstAK CI7jh9pNg+ Of16s1nJ6rKgegA pHACdFr63 VNMUbugm9mesUM=
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFHa95w0F+
79LOp+0H+
=kSyJ
-----END PGP SIGNATURE-----