>> I like separating out the "get a new module" concept from the
>> "pull in changes from the server" concept.
>Those two concepts are legacy concepts. You view establishing a working
copy
>as an operation and a result in its own right. I see "fetch me the files".
<delurk>
Well I have to admit I have spent about an hour yesterday training someone
the difference between co and update.
Any experiences from other systems that may help, especially the ones with
similar directory type models?
>From a usability point of view I see the 2 different use cases (cvs model):
- tagging a whole tree as a release (simple with svn as planned)
- tagging/branching individual files throughout the tree for reviews
(involves identifing files easily, building them with HEAD to test,
comparing with HEAD, commiting comments to branch, merging branch to
HEAD
I do't know how simple that is in the svn model)
</delurk>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:48 2006