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

RE: VisualSVN server, TortSVN - merging revisions

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Wed, 1 Sep 2010 15:05:52 -0400

> On aug. 31, 21:27, Felix Saphir <felix.sap..._at_kantarmedia.de>
> wrote:
> >
> > The file is never deleted, it's just no longer present in a newer
> > revision. But it's still there on the server in your repository.
>
> I know this. This is the problem. 1,5 GB binary (database) files
> are
> remains nevertheless - they are uploaded, but we don't use them -
> only
> hold the disk space.
>
> >
> > > As I think merging is also release space if you have many
> revisions
> > > with many differences.
> > > Because differences are need to store, but if you merge them,
> you can
> > > see only the last version, what is hold less disk than
> before...
> >
> > Your working copy might be smaller, yes.
>
> If I can dump and I can load it, I can decrease the used space.
>
> >
> > If you really worry about the size of your repository, buy a new
> disk.
>
> This is not too simply: we have virtual server, we bought fix HDD
> size, this is the limit.
>
> Thanks:
> dd

Have you considered using maven or some other system that is designed to manage binary version using the file system?

Are they binaries not buildable from source checked into your svn repository?

Our build system stores the artifacts of the build (the binaries and other deployables) in the file system of the build server which is shared out. The build system cleans up after it self keep only the artifacts of the last 5 builds of each project/major.minor version.

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2654192

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-01 21:06:04 CEST

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