Push location hiding

[Aaron Bentley]

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

Stefan Monnier wrote:
>> So when might it matter that the push location is stored in branch.conf?
> 
>> Generally if the branch is a shared branch, i.e. multiple developers are
>> committing to, and pushing from, the same branch.
> 
> I must say I do not understand.  Could you give a scenario where giving
> priority to branch.conf over locations.conf would introeduce a problem?

It is always a problem to prefer potentially read-only configuration
data over read-write configuration data.

In this case, say we push over bzr+ssh.  The url is: "bzr+ssh//foo/bar"

But my username on "foo" doesn't match my local username.  Unlike the
rest of the team, I need to specify "bzr+ssh//bentleya at foo/bar".

If branch.conf is authoritative, I cannot fix the URL for me without
disrupting the others.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIWnks0F+nu1YWqI0RAq1TAJ91j7yB2F7L0XOTHOUQNlFLreN7oQCeJhQH
j0vXSlufxL4wXgfeUOuEkGQ=
=eBnN
-----END PGP SIGNATURE-----