[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion vs CVS for document files

From: Eric <spamsink_at_scoot.netis.com>
Date: 2006-11-15 16:02:16 CET

At 12:46 PM 11/14/2006, Duncan Murdoch wrote:

>> This is only a problem if you're desperately searching for problems.

Good morning, Duncan.

It is a problem if you're working with people who are absolutely convinced
that it brings no benefit, and whose minds can't be changed.

I can say "I can check out a complete set of files at rev X and I'm
guaranteed that the spec matches the design matches the code matches the
tests" and I hear "Yeah, yeah, you can do the same thing with VSS with
tags" or some such.

Never mind that it takes extra steps with VSS or CVS or most other VCSs,
and you get it automatically with SVN.

There are still document files, though, where it makes no sense to try to
tie them to other files in a repository (e.g. company policies and
procedures, correspondence, etc.) and it remains cumbersome to put each of
them in its own repository. You can argue that it's not "bad", per se, to
bump one revision level for largely-unrelated collections of such files,
and that it does no harm, etc., but I will NEVER, ever, be able to convince
the others on this team of that, even though I might, someday, be able to
convince them to grudgingly accept the notion of a common rev number for a
whole repository of RELATED files.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 15 16:03:57 2006

This is an archived mail posted to the Subversion Users mailing list.