Re: Selling no '.cvsignore'

>> 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.

I can verify this myself. I use both svn and cvs, and have a tendency
to use "cvs -q -n up" or some other variant of it to check the
actual status. Separating status and update is good.

Cheers,
Marcus

-- 
Marcus Alanen
maalanen@abo.fi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org