Push location hiding

[Barry Warsaw]

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

On Jun 18, 2008, at 12:00 PM, Aaron Bentley wrote:

> John Arbash Meinel wrote:
>> Everything thinks it is okay. However the push location is saved to
>> .bzr/branch/branch.conf. And 'locations.conf' overrides branch.conf,
>> even though one is achieved recursively, and the other is  
>> explicitly for
>> that branch.
>
> The rationale for making locations.conf trump branch.conf was because
> locations.conf is unambiguously under the user's control and can be
> changed without affecting others.

Does that mean that when I push, and someone branches my branch,  
they'll see my branch.conf?

> The rationale for making recursive locations.conf rules trump
> branch.conf values was avoiding extra complexity in the user model.
>
>> I don't have any way to force the remember, other than manually  
>> hacking
>> locations.conf for that branch.
>>
>> Is there something better that we could be doing?
>
> We could set it in BOTH branch.conf and locations.conf, I suppose...

I'd rather not clutter up my global locations.conf with lots of branch  
specific stuff.  I do think that --remember ought to remember.   
Perhaps there should be a .bzr/~user/locations.conf or some such that  
only affects my branch on this machine.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSFkyHXEjvBPtnXfVAQJpkwP/X1RFI3/WX+ThqSr+sqga7Qo9QDZmFakg
15QeztXUknQsszOvHEXsUVca2zUmvUBjQBbh8izKLBcVDU0IulhuKrn1DpLMIv7r
kYw/qEnYyS8VMxVdQ1sA+6tUcH2KlTNy44Wlf4Bc2vIIFZHupKuMtHrjdM2IrgVT
6g9MxSottaY=
=HwJI
-----END PGP SIGNATURE-----