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

Re: Copy-To (forward reference) info in FSFS or BDB?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 12 Nov 2009 11:22:21 -0500

Julian Foad wrote:
> On Wed, 2009-11-11 at 09:17 -0500, C. Michael Pilato wrote:
>> Julian Foad wrote:
>>> For obliteration, I need to be able to find all back-references from
>>> newer revisions to the node-rev I'm obliterating.
>>> Did we ever get anywhere with implementing a table to cache forward
>>> references ("copy-to")?
>> http://svn.collab.net/repos/svn/branches/fs-successor-ids/ ?
>> Successor-ids + copyfrom info = copyto_info (effectively).
> Cool. I've sync'd the branch to trunk, and it builds and passes
> regression tests (though there are no tests for the new functionality).
> Next, I'm making the format bump, FS-BDB format going from 4 to 5, and
> making this successor-ids table conditional on format >= 5. Patch
> attached. Is this correct?
> After that, two possible next steps are:
> * to connect the APIs up through the layers (FS -> repos -> RA ->
> client) so that a client can use it.
> * to add some tests at the FS layer.
> * to investigate how to do the equivalent in FSFS. (Stick a table in
> the sqlite db?)

I count three possible next steps here, not two, but at any rate, please
allow me to order them for you:

   1. add some tests as the FS layer.

   2. do the equivalent in FSFS *OR* get dev buy-in for allowing backend
       feature sets to diverge.

   3. add APIs through the layers between FS and client.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2009-11-12 17:22:41 CET

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