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

Re: Pros and cons of significantly large repositories

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-04-10 18:50:36 CEST

Andrew R Feller wrote:

> I agree that most people use version control for application code bases,
> however, I think you will find that many people use it for its intended
> purpose: to track changes in whatever documents/files you deem important
> to review and maintain over a length of time by multiple people. If you
> don’t care about history and being able to revert mistakes, then by all
> means use rsync and keep the files on your filesystem outside of
> Subversion. I don’t see how Subversion or any version control system is
> a “code only” tool and I believe most people would agree with that.

Not necessarily code-only, but there are certain features (like readable
diffs) that only work with text files, and there are certain issues
(like never being able to delete anything) that may be more problematic
if you allow many large and obsolete binaries to accumulate. If you do
want use svn as a convenient mechanism for storing and accessing files
when you know that older versions will never be wanted, you might want
to put them in separate repositories that can be restarted periodically
to clean them up instead of having to dump/filter a huge repository
later to sort out what you want to keep. If you access via http(s),
this can be almost transparent.

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 10 18:51:03 2007

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