On Oct 18, 2005, at 18:00, Cyrus Jones wrote:
> Thanks for the response on my earlier question. The reason I asked
> is that I ran a test with a large compressed fil. I checked this
> file in on my development machine and the I then checked out the
> file on a second machine. I then modified the file and made several
> random changes throughout the file and checked that in. When I
> updated the file on the second machine it appears that SVN simply
> pulled the entire file down instead of just the changes. Is there
> some kind of threshold where if a file is too "noisy" that SVN
> simply resorts to pulling down a new copy?
Not that I'm aware of.
By what means did you determine that Subversion was doing this?
Depending on the compression algorithm you used, the modified
compressed file may bear little resemblance to the original
compressed file. This applies to some other binary formats too.
Subversion will still work fine, it's just that the space savings the
differencing is supposed to achieve aren't necessarily realized
there. It works best for uncompressed text files.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 18 22:58:02 2005