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

Re: svn commit: r19923 - in trunk: . build/ac-macros

From: David James <djames_at_collab.net>
Date: 2006-06-04 23:28:59 CEST

On 6/4/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 6/4/06, Max Bowsher <maxb1@ukf.net> wrote:
> > Any particular reason? Bear in mind that we have a virtual certainty of
> > having code using it before the next release.
> Until we actually have code that uses it there is no certainty at all
> that it will be used in the next release, IMO. For all we know Vlad
> could get hit by a bus tomorrow and nobody will pick up this work.
> It's unlikely that such a thing would occur, and we certainly hope
> that his work will progress to the point where it is incorporated into
> the next release, but it's not a certainty.

Could we take a 'wait and see' approach here? It's easier to commit
patches directly to trunk, and as long as these incremental patches
work, I don't see any reason why they'll cause any harm. If Vlad does
get hit by a bus, I'm sure there are lots of other people who would be
willing to step up and finish the SASL support.

We took this same approach for ra_serf (i.e. work directly on trunk)
and it turned out quite well for us. I think that extra exposure,
review and testing of the SASL patches can only be good for our SASL



David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 4 23:29:23 2006

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