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

Re: Merging /branches/integrate-cache-membuffer to /trunk

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 28 Jan 2011 06:56:15 +0200

We could ask ASF infra to enable the "optional" feature on svn.eu
(without enabling it on svn.us).

The experimental code gets tested, and if it cooks the disk alive and
burns the data then we (pay for a new disk and) svnsync svn.us to svn.eu :-)

Stefan Sperling wrote on Wed, Jan 26, 2011 at 23:42:05 +0100:
> On Wed, Jan 26, 2011 at 11:25:59PM +0100, Stefan Fuhrmann wrote:
> > Hi @all,
> >
> > I'm planning to merge said branch Monday 7th.
> > Speak now or forever hold your peace.
> >
> > Rationale:
> >
> > I've been testing / using that code for a while now
> > and am reasonably confident that it works. And it
> > is not exactly rocket science, either.
> >
> > Because a large portion of my other performance
> > work builds upon that low-latency caching feature,
> > it would really like to see it being merged. Directly
> > after the merge, I will make the feature strictly opt-in
> > instead of defaulting to a 16 or 64 MB cache.
>
> I'd say merging to trunk is perfectly fine if you're confident that
> there aren't any roadblock issues and it's not enabled by default anyway.
> We've released optional new features in the past (e.g. libsvn_serf).
> It's much more likely to get tested this way :)
>
> Stefan
Received on 2011-01-28 06:00:43 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.