[MERGE] Make 'missing' try the pushloc too

[John Arbash Meinel]

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

Robert Collins wrote:
> Robert Collins has voted -1.
> Status is now: Vetoed
> Comment:
> I dont think makes sense: missing is used as the way to find out what
> you have not grabbed yet - it shows 'unmerged/unpulled' revisions -
> using the push location is not intuitive or predictable. Using the
> /bound/ location as a fallback might be nice, though I'm ambivalent on
> that (I think an 'update --dry-run' or 'update --missing' might be nicer.)
> 
> What prompted you to create this patch?
> 

Well, 'bzr missing' is symmetric. So if it uses the push location, it
can tell you whether you have anything to push.

Logically, "bzr missing --mine-only" would go to the push location and
"bzr missing --theirs-only" would go to the pull location.

Not that I'm advocating for the patch, mostly because it means the
default location may be jumping around on you, which is likely to
confuse more people than it helps. (If it was using push until you did a
merge, which set the parent location, and then it continually uses that
location...)

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGI5slJdeBCYSNAAMRAjzQAJ9eeTiqL9JNxFlRJAvRNqLzK60kBwCeI967
I3i2BvsCU5ZcHLbikAoGbx8=
=zpoh
-----END PGP SIGNATURE-----