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

[Aaron Bentley]

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

John Arbash Meinel wrote:
> Aaron Bentley wrote:
> 
>>John Arbash Meinel wrote:
>>
>>>>Aaron Bentley wrote:
>>>>
>>>>
>>>>>Using heavyweight checkouts instead of lightweight ones with remote
>>>>>branches is just a convention.  So doing this does require a connection
>>>>>to the branch, which is a new requirement.
>>
>>>>Well, at present because of the way 'BranchReference' is defined, we
>>>>always connect to the remote branch, for any lightweight checkout.
>>
>>Right.  That's why I phrased it as I did.
>>
> 
> 
> ...
> 
> 
>>out of date (use "bzr update"):
>>    branch is at: "Fixed a really nasty bug"
>>
>>But I'm fine to put it in as the warning, and then worry about tweakage.
>>
>>Aaron
> 
> 
> Ooooh a summary line of the last commit. Fancy. :) (I really do like it).
> 
> So, would you be +1 if we got rid of the warning in 'diff', and then
> encourage Cheuksan to extend his patch to change 'bzr status' to conform
> to this?

Yes, that would suit me well.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFQjSq0F+nu1YWqI0RAi8bAJ0SRv33dTg4Shp/XtgJO2+tlQY+5gCeKQDs
1+WVVFKUGb4QWsXnOOeK3gY=
=UWNy
-----END PGP SIGNATURE-----