Delta not showing modifications sometimes

[James Blackwell]

On Tue, Nov 15, 2005 at 06:29:48PM -0500, jblack wrote:
> Yeah. Having the UI displaying only one changed state at a time doesn't
> match with behaviour that the users know better about. Newer users could
> wrongly assume that bzr can't walk and chew gum at the same time.
> 
> If the user builds up too many of these sorts of surprises before they hit
> the docs and grok what's going on... well, they probably move on and look
> for another tool that behaves 


This doesn't mean that bzr isn't an awesome tool made by incredible
hackers (because I'll jump at the chance to go toe-to-toe with anyone that
disagrees!) Expectations are like opinions; no two people have exactly the
same ones.  There's probably no right or wrong answer in something like
this. 

My strawman for this particular opinion is the prototypical american that
is more inclined to use something without bothering to read the
instructions -- something that is excaberated by the success in making bzr
as simple to use as possible. 

I don't think anyone would be surprised with status showing only one move
operation with a "bzr mv a b; bzr mv b a" because the second mv
essentially cancels out the previous mv. 

But if the user modifies a file and renames it, then two orthogonal
actions have happened. They should thusly both be reported during status.
Otherwise, the user (even an experienced one) can be tricked by doing a
status to verify the tsatus, see only a change, and found out there was a
modification there as well.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051115/dd629668/attachment.pgp