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

Re: Strange format file problem

From: John Szakmeister <john_at_szakmeister.net>
Date: 2005-11-02 10:55:33 CET

On Tuesday 01 November 2005 22:23, Daniel Berlin wrote:
> On Tue, 2005-11-01 at 16:15 -0500, John Szakmeister wrote:
> > Blake McBride wrote:
> > > See:
> > > http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=5680
> > > <http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=568
> > >0>
> > >
> > > It seems to indicate that I have the wrong format.
> > > It says that I should have a "3" or I am using an ancient format.
> >
> > I believe there was at least 1 dump due to using xdelta as the new
> > compression algorithm instead of vdelta.
>
> This did not cause a bump, because the change is not visible at that
> layer.

That's right! I used the handy 'svn log' was bumped once because the schema
changed to help several correctness and performance problems. It appears the
other bump came from the fact that we wanted format files associated with the
repo, and the particular backend that was being used (so we could version
those separately than the repository itself).

Blake, you might want to do a dump and load when you get a chance. The bump
to format 2 had the following in the log message:
  Merge the net changes from of the 'fs-schema-changes' branch to the
  trunk. This completes the following issues:
     issue #1003 - svn_fs_revisions_changed() needs some fixes
     issue #1248 - 'svn log --strict' on a copy doesn't show all mods
     issue #1438 - performance decreases with number of revisions

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 2 10:57:40 2005

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.