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

Re: svn commit: r14182 - branches/1.2.x

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-04-14 09:22:20 CEST

On Thu, 14 Apr 2005, C. Michael Pilato wrote:

> "Peter N. Lundblad" <peter@famlundblad.se> writes:
> > > Make the public locking API semantics for lock expiry match the internal
> > > storage and known concerned caller's semantics.
> >
> > Does this require a restart of the 4 week soak? (We may want to do that
> > anyway, just wanting to be sure.)
> That depends on whether or not the change is considered destabilizing.
> I don't personally think that it is.
I was thinking about the API incompatibility clause of HACKING, but it was
no requirement to restart, just a recommendation to be careful.

I agree it shouldn't be destabilizing according to the log. Haven't
reviewed yet.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 14 09:17:22 2005

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