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

Re: [Issue 3815] New - incremental hotcopy, fsfs-only

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 19 Feb 2011 10:42:53 +0200

philip_at_tigris.org wrote on Fri, Feb 18, 2011 at 14:16:29 -0800:
> http://subversion.tigris.org/issues/show_bug.cgi?id=3815
> Issue #|3815
> Summary|incremental hotcopy, fsfs-only
> Component|subversion
> Version|---
> Platform|All
> URL|http://svn.haxx.se/dev/archive-2011-02/0582.shtml
> OS/Version|All
> Status|NEW
> Status whiteboard|
> Keywords|
> Resolution|
> Issue type|FEATURE
> Priority|P3
> Subcomponent|svnadmin
> Assigned to|issues_at_subversion
> Reported by|philip
>
>
>
>
>
>
> ------- Additional comments from philip_at_tigris.org Fri Feb 18 14:16:28 -0800 2011 -------
> http://svn.haxx.se/dev/archive-2011-02/0582.shtml
>

You still haven't answered my question:
http://svn.haxx.se/dev/archive-2011-02/0583.shtml

> It should be possible to implement "svnadmin hotcopy --incremental" for FSFS
> repositories. This would only need to copy rev files newer than HEAD of the old
> copy, rather than all the rev files.
>
> An incremental hotcopy would need to account for changes in packing, both of rev
> files and revprop files.
>
> It would need some strategy to deal with old revprops: copy all of them, read
> and copy those that have changed, copy those with newer timestamps.
>
> Finally it would need to deal with exclusive file locks, probably by deleting
> all the locks and copying a new set. See also issue #3750.
>

Regarding revprops and locks, synchronize them using the same methods
that the WebDAV mirror feature uses.

> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2705446
>
> To unsubscribe from this discussion, e-mail: [issues-unsubscribe_at_subversion.tigris.org].
Received on 2011-02-19 09:48:12 CET

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.