Re: Selling no '.cvsignore'

Dirk-Willem van Gulik <dirkx@webweaving.org> writes:

> I take that this default was choosen for a reason.
>
> Any pointers to some documentation/list which can help me 'explain' why
> the current __default__ silent behaviour is better ?

Yes. We've very deliberately separated 'svn status' from 'svn update'
behaviors. We think it's bad design that CVS blurs the two ideas.
Notice how CVS users habitually run 'svn up' just to find out what
files they've modified, or to see if there are any unversioned files.
Really, if 'cvs status' weren't so hard to read, it should be giving
them that information instead.

So cvs users switching to svn need to re-habituate to running 'svn st'
whenever they want to learn about their working copy. 'svn commit'
and 'svn up' will only describe what's been sent or received.

This topic is covered in the "SVN for CVS Users" appendix of the SVN
Book:

  http://svnbook.red-bean.com/book.html#svn-app-a-sect-3

You might want to glance over the whole appendix, actually.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 13 15:46:30 2003