[Bug 49742] Re: last push location not saved

[Olaf Conradi]

On Wed, Jun 14, 2006 at 02:29:25PM -0500, John Arbash Meinel wrote:
> I agree with that. Same for the first pull that succeeds. The code is
> easy to fix, we just need to move the point where it saves the reference
> to just after the pull/push finishes.
> 
> Sending this to the mailing list to get a discussion on it.

When I implemented this, the rationale for the first action was:

$ bzr pull/push/merge location
<some error because of working tree state>

Fix error depending on command, like resolving conflicts, or update
out-of-date tree, or diverged tree, etc.

And repeat last instruction, without needing to specify the location.

$ bzr pull/push/merge

For consistency between the commands, the behaviour is the same for pull,
push, and merge. If we change one, we should change the others too.

So the question is: What is the most frequent use-case for the initial
operation in case of failure.

1. Is it making a typo in the location name, meaning you don't want to
remember after a failure.

2. Or is it because of the state of the tree and you command was
correct.

 -Olaf