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

[John Arbash Meinel]

Matthew D. Fuller wrote:
> On Fri, Oct 27, 2006 at 10:32:14AM -0500 I heard the voice of
> John Arbash Meinel, and lo! it spake thus:
>> info:
>>   Local tree is out of date with branch, use 'bzr update'
> 
> Veering off into another topic:
> 
> Somewhat related to this is the irritation that you can't SEE what rev
> the working tree is at.  The closest you can get is to guess by doing
> a bunch of math from the 'info' output (though even that doesn't help
> you if you're not at a rev on the mainline), and 'revno' helpfully
> tells you the branch head number, which is totally misleading.
> 
> Of course, that also ties into "You can't 'update -r' a working tree";
> all you can do is revert, and that causes all sorts of troubles (try
> it: "bzr branch bzr.dev tmp; cd tmp; bzr revert -r500; bzr revert
> -r-1"; blech!)...
> 
> 

Well:

1) We really do want to get update --revision merged. I'm not sure why
it has languished, other than some small disagreements on exactly when
revision specs get transformed into revision identifiers.

2) 'bzr revno' should probably be the revision of the working tree

3) 'bzr log' should show the revisions of only the working tree,
possibly with a warning about being out of date. Or possibly it could
show both, but somehow mark the ones that are not present in the working
tree.

There are a few places we need to clean up. And we also want to be aware
of heavy versus lightweight, and try to get them functioning in unison
as much as possible.

I agree, there is a lot that can be cleaned up here.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061027/1812d1d8/attachment.pgp