[patch] fix bug 48136 bzr status, diff, etc do not work properly after remote push

[Matthew D. Fuller]

On Fri, Oct 27, 2006 at 11:10:31AM -0500 I heard the voice of
John Arbash Meinel, and lo! it spake thus:
> 
> 2) 'bzr revno' should probably be the revision of the working tree

Ideally, I'd say it should say both (maybe collapsed down to 1 if
they're the same).  I'm a bit leery of changing it, though; if ever a
bzr command were written as if to be used as "plumbing", 'revno' is
it; most people frown on programs that blow up their scripts.  I don't
know how big a concern that is in the community at this point (or how
assiduous we want to be about preserving such things pre-1.0).


> 3) 'bzr log' should show the revisions of only the working tree,

This I'm a little more iffy on; I think of 'log' as referring to the
branch.  But that also veers even FURTHER off course, and belongs in
another email that's currently brewing in my mind.  Maybe I'll acquire
a round tuit for that together later today...


> And we also want to be aware of heavy versus lightweight, and try to
> get them functioning in unison as much as possible.

And don't forget also that we have a third form of working tree; that
directly associated with a branch.  I may (and do) want to fling that
around old versions and back to head too.  And it's the one that gets
out-of-date from a 'push', too.


-- 
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.