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

1.4 CHANGES and svndiff1

From: Daniel Berlin <dannyb_at_google.com>
Date: 2006-06-07 14:36:29 CEST

1.4's changes file doesn't mention svndiff1, but probably should.

I through together some draft notes on upgrading a repo to svndiff1
encoding.

Feel free to tear them to pieces.

SVN 1.4 includes a new delta encoding that is used over the wire and
on disk, when possible. This delta encoding is much more space
efficient, which is a boon to high latency and slower connectios.
There is nothing that needs to be done in
order to keep older clients working. New clients and servers will use
the new format if both sides support it.
In order to use the new encoding in on-disk repositories, a dump and
load must be performed. SVN will not use the new encoding on existing
repositories, in order to preserve backwards compatibility.

UPGRADING A REPOSITORY TO SVNDIFF1

Note: THIS IS COMPLETELY OPTIONAL. If you do not upgrade your
repository's delta storage format, everything will still function
normally, including all older and newer clients that use direct
access. You simply will not gain the space savings.

Further note: Do not do this if you have programs that need direct
access to the repository (servers or clients using file://), but can't
upgrade to 1.4+, as the older clients will not be able to understand
the new repository format. This does not apply to clients that connect
through servers (http or svn access methods).

In order to convert a repository to svndiff1 encoding, simply create a
new repository using svnadmin create, and svnadmin dump/load your old
repository into it.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 7 17:40:42 2006

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