"bzr status" in a lightweight checkout

[Martin Pool]

On 11 August 2010 17:50, Stephen J. Turnbull <stephen at xemacs.org> wrote:
> The thing is, I can't really see a use case for a lightweight checkout
> of a personal branch (which might be a mirror of upstream, the point
> is that it's local) that isn't equally well-served by git-style
> colocated branches with shared repositories.  AFAICS lightweight
> checkouts only have semantic significance if checkouts are used to
> ensure frequent synchronization of team's work.  But in that case I
> would expect that the branch is likely to be located across a network,
> possibly a WAN, in which case going out on the network as a matter of
> course is a recipe for unnecessary latency.

There are two main interesting cases for having a wt out of date with
its branch:

-  'bzr update -r REVID' to temporarily go back and look at an old
revision; presumably in git you would just make a temporary branch
coming off that revision

- pushing changes into another branch across a dumb protocol without
updating its tree; you can then run 'bzr update' on the remote
machine.


-- 
Martin