<br><br><div class="gmail_quote">On Thu, May 7, 2009 at 9:17 AM, Ian Clatworthy <span dir="ltr"><<a href="mailto:ian.clatworthy@internode.on.net">ian.clatworthy@internode.on.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I've spent today putting down on paper how *I* would like nested 'items'<br> to look from a UI perspective. Not all of this will arrive in the<br> initial cut but I wanted to dig deep enough so that we could debate the<br> initial design in a broader context.<br> </blockquote><div><br>One more comment. You are not the first to do this but using the word "branch" to casually mean "root directory of the working tree" or "root directory of the nested tree" is potentially confusing. When I am teaching people to use vcs -- subversion, bzr, perforce and (gasp!) clearcase -- I am amazed that novice users need to be told over and over the distinction between a branch and a working tree (or a view or a checkout or...). The vcs world is full of things which should be clear from context but are not because new users hear old users speaking casually. I am guilty of this too, of course. I do not have a good answer. I just try to write "directory" when I am talking about the working storage and it seems to help people understand that working storage is just bits on disk but branches are magical things with history. This distinction is even harder to communicate with dvcs than with client-server setups, so I have to make extra effort. Anyway maybe this is just my expereince.<br> <br>-M<br><br></div></div>