Changing the UI of checkout

[Stephen J. Turnbull]

Matthew D. Fuller writes:

 > [commit --local] IS a bad command, though.  Kinda.  It's coloring
 > outside the lines.  The whole point of a checkout is that you're
 > just a working tree on a given branch; you don't go out of sync in
 > such a case,

Of course you do.  As soon as you save a change, *you're out of sync*.

To protect your work, there should be a place to commit it.  You can't
guarantee that you can commit to the remote branch unless it supports
multiple heads and repository policy allows you to do a push that
creates a new head.  Bazaar doesn't support the former, and the latter
is generally frowned upon anyway.  What's left is "commit --local".

The whole idea of checkouts with "working trees" is ill-conceived.
Checkouts as source distribution for end users and beta testers are a
wonderful idea.  But anybody who makes changes to the code is putting
themselves in harm's way by doing it in a checkout.

Bound branches are another matter.  I'm not a big fan of workflows
that use them, either, but at least the idea is theoretically sound.