Selling no '.cvsignore'

During a few evals of SVN one item related to .cvsignore kept poping up
indepdentenly. Mostly by experienced development managers which have to
work with relatively green (java) programmers who are under a deadline and
not yet had been involved in any serious car craches or foodprocessor
accidents.

By -default- a 'svn update' or 'svn commit' does not scream bloody murder
when it encounters any files not under svn control.

Whereas CVS (and most of its competitors) have more of a tendency to be
obnoxious and force the developer to keep their .cvsignore files in order.

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 ?

Txs,

Dw

---------------------------------------------------------------------
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:22:51 2003