Is this right? now discussing the use of --remember

[David Ingamells]

Andrew Cowie wrote:
> On Tue, 2008-11-04 at 10:57 +0100, David Ingamells wrote:
>
>   
>> It looks to me that the only way to update the parent reference is to do 
>> an action that might update the contents of your local branch
>>     
>
> For what it's worth, you can always hand edit .bzr/branch/branch.conf
>
> I find that a bit distasteful, but it is a workaround for the command
> line UI hassle you describe.
>
> AfC
> Sydney
>
>
>   
Thanks, that could be a workaround if the need ever arises.
I agree, it is distasteful as there is no sanity check.

Might I propose that a command like "bzr missing" could be extended to 
support the --remember argument; but it should only remember if the new 
location looks sensible. bzr missing already supports an OTHER_BRANCH 
argument.

Some background. I have (quite coincidentally) just had a discussion 
with a colleague about what would have to happen if our repos server 
died and we had to use the backup of it served from another location. 
All developers with a local branch would have to update their parent 
location, but it is preferable not to force developers to merge parallel 
updates until they are ready to do so, so updating the location via bzr 
pull or another command that does support --remember is undesirable.