Thanks for the link--I didn't know about this. Still,
switching to SVN would probably aggravate the problem,
by draining users and developers away from CVS--hence
slowing CVS' bug fixes and greater security
enhancements.
There's nothing magical about SVN--it is open source
too and subject to the
On Jun 11, 2004, at 10:35 AM, Glen Mazza wrote:
Thanks for the link--I didn't know about this. Still,
switching to SVN would probably aggravate the problem,
by draining users and developers away from CVS--hence
slowing CVS' bug fixes and greater security
enhancements.
There's nothing magical
I don't know who this should go to (they probably already know), but
according to Reuters[1], the CVS system has some fairly significant
holes. I know Forrest moved to SVN not too long ago. Have we thought of
doing it ourselves?
Web Maestro Clay
[1]
There's a big push within Apache to adopt Subversion, and I suppose it
will get to us in the near future. However, if we go there, I don't
think it would be for this reason primarily. What are the security
vulnerabilities of SVN? Nobody knows yet, and SVN has not been
targeted. At least
