[MERGE] Make 'missing' try the pushloc too

[Matthew D. Fuller]

On Fri, Apr 06, 2007 at 12:32:07PM -0400 I heard the voice of
Aaron Bentley, and lo! it spake thus:
> 
> I think you could make the case for running missing against the
> parent location, push location, submit location, public location,
> maybe even bound location.  (And personally, I think we need a
> "merge location", too.)
> 
> It's too much.  I think we should seriously look at an alias system
> so you can do "bzr missing :push" or something.

This strikes me as 3 separate, if related, issues.

1) 'missing' should do something useful if called without a location.

2) 'missing' should be able to be run on [one/any of] the branch's
   saved locations without having to enter the URL manually.

3) We need location aliases.


I tend to rather prefer (2) as an option rather than as syntax, and
(3) the other way around.

In this case, though, I'm looking purely at (1).  If I have stored
locations for a branch, missing should use them in preference to doing
nothing if I don't give it an explicit notification.  In particular, I
have lots of branches with pushlocs and no parent, that I want to
'missing' on with some regularity.  For a number of them, I ended up
just "giving in" to the shortcoming and setting the parent to the
pushloc.  Today, it bugged me enough to patch.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.