Push location hiding
Aaron Bentley
aaron at aaronbentley.com
Tue Jun 24 02:56:52 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stefan Monnier wrote:
>> All branches can be accessed directly all the time.
>
> And when would it be a problem if this remote branch's branch.conf is
> obeyed in preference to the user's locations.conf?
I wasn't arguing that, especially. You were:
> I think it's just wrong for branch.conf to ever not be under the user's control.
However, there are some values that might be useful to override on a
read-only branch
- - public_branch
- - child_submit_to
- - bound
Mostly, overriding these allows the user to compensate for inappropriate
settings. Disabling bound would allow the user to interact with a
heavyweight checkout whose branch had gone missing.
More generally, the user should always be in control. To the extent
that remote sites can set a policy, users should be able to override
that policy.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIYFRk0F+nu1YWqI0RAl5FAJ9lBrNDNjRqJHRKXKyjFg20bMqhfQCeKuFD
oyaGaWDZngf2FgFKCIsNt/Y=
=J9c/
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list