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

Re: how issue-2897 branch solves reflective merges?

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 21 Jan 2008 10:31:47 -0500

On Jan 21, 2008 10:20 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Jan 11, 2008 2:45 PM, David Glasser <glasser_at_davidglasser.net> wrote:
> > My personal preference would be to merge reintegrate to trunk in the
> > very near future; then update issue-2897 based on that, then to (on
> > the 2897 branch) reimplement the FS API without SQLite (I'll do that),
> > while concurrently folks review Kamesh's libsvn_client changes (not
> > the backend, which as I said I'll rewrite). Then merge that back to
> > trunk, then remove the SQLite dependency (which also involves
> > rewriting the node origin cache on FSFS only, which will be very
> > easy... just store them as small files in a directory or something),
> > then BRANCH 1.5.
> This sounded like a good plan. How are we doing? Step 1 was to get
> reintegrate merged to trunk. What is left to do for that to happen?
> Also, are there any opportunities to divide this work up so that it is
> not all on your shoulders?

Looking at your list again, it looks like a good item that could be
taken off your shoulders would be rewriting the node origins cache to
not use SQLite. Could you file an issue or post something to dev@
that describes how you would do it? Then maybe someone else could do
that while you are updating the issue-2897 branch?

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-21 16:32:01 CET

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