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

Re: How to avoid pristine copy for really big files?

From: Chris Frost <chris_at_frostnet.net>
Date: 2007-09-09 21:07:25 CEST

On Wed, Sep 05, 2007 at 10:33:21AM +0200, Erik Huelsmann wrote:
> On 9/5/07, Christian Convey <christian.convey@gmail.com> wrote:
> > I've got a project that has some really big binary files checked into SVN.
> >
> > The files are so large (relative to the amount of available
> > client-side storage) that I'd really like to avoid having Subversion
> > keep two copies of each file on the client side: one exposed copy,
> > plus one pristine copy under the .svn directory.
> >
> > Is there any way I can get this down to just one client-side copy
> > rather than two?
> Hi Christian,
> We have wanted to address this issue for a long time now, but
> unfortunately, it's been blocked by other important/more important
> features.
> This issue is tracked in the issue tracker, here:
> http://subversion.tigris.org/issues/show_bug.cgi?id=525

Christina, in case you are using a unix, I am finishing up a virtual
filesystem that detects when the working and pristine copies are
identical, and stores them just once. It's not quite at what I want to
call v1.0 yet, but v0.9 is stable as far as I know:
v1.0 will include OSX support (already checked in) and probably a few
other improvements.

There are some tradeoffs that come with scord (or at least, the current
implementation), like slower file system syscalls, but it might nonetheless
be interesting for you? The scord website describes the tradeoffs.

I definitely plan to announce v1.0 here.

Chris Frost  |  <http://www.frostnet.net/chris/>
PGP: <http://www.frostnet.net/chris/pgpkey.txt>
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Sep 9 21:04:21 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.