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

Re: svn commit: rev 2320 - branches/issue-745-dev/subversion/libsvn_fs branches/issue-745-dev/subversion/libsvn_fs/util

From: Branko Čibej <brane_at_xbc.nu>
Date: 2002-06-24 10:40:37 CEST

cmpilato@tigris.org wrote:

>Author: cmpilato
>Date: Mon, 24 Jun 2002 03:11:54 -0500
>New Revision: 2320
>
>Modified:
> branches/issue-745-dev/subversion/libsvn_fs/fs.h
> branches/issue-745-dev/subversion/libsvn_fs/reps-strings.c
> branches/issue-745-dev/subversion/libsvn_fs/structure
> branches/issue-745-dev/subversion/libsvn_fs/util/fs_skels.c
>Log:
>Add version number to "svndiff" database storage mechanism. Idea
>gleaned from a patch by Daniel Berlin <dan@dberlin.org>. From this
>point, Daniel's implementation of svndiff v.1 (also present in the
>patch, but not of strict interest my task at hand) can be added
>without requiring a repository dump/load cycle. While this change
>*could* have been implemented to be backwards compatible, forthcoming
>changes to the filesystem code will not be, so a dump/load cycle will
>be required for all existing repositories anyway. I'm considering
>this change part of Issue #745.
>
>
Oh, coolness. I meant to do this as part of activating the delta
combiner; this is even better. :-)

It does raise a small issue, though. The delta combiner integration will
touch the same part of the code -- specifically, rep_read_range() in
reps-strings.c. In light of that, it might be best to do the combiner
change on this branch, rather than on the trunk. But that might limit
your (our) artistic freedom somewhat. :-)

Thoughts?

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 24 10:42:54 2002

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

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