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

Re: [RFC] [PATCH] Allow any Neon version from specified branches

From: Greg Stein <gstein_at_gmail.com>
Date: Sun, 21 Sep 2008 21:37:36 -0700

On Sun, Sep 21, 2008 at 8:33 PM, Peter Samuelson <peter_at_p12n.org> wrote:
> [Greg Stein]
>> [please review the PATCH mail submission guidelines in hacking.html;
>> it was very difficult to review your patch as emailed]
> Shrug - it came through my MUA inline.

Not all MUAs do, which is why we established some guides. When it
becomes hard to read, then people simply don't. Arfrever and I had
discussed this before, so I was motivated. If it had been for (say)
the client lib? Nah. I wouldn't have looked at it, and that is Not

>> In the past, we have had issues with Neon (with all dependent
>> libraries, actually). I prefer that we only allow known-good
>> libraries, rather than open it to "anything on this branch".
> We don't do that for other software we use, such as Berkeley DB. And I
> don't think we should. All software has bugs, and I don't think it's
> our responsibility to detect buggy versions of unrelated software.

If we *know* about buggy subsystems, then it is incumbent upon us to
decline to work with those versions.

In general, I believe that I agree with you and Arfrever that maybe we
can be more lax in our version checking on subsystems. With respect to
Neon, we should disable 0.27.{0,1} and not (yet) support 0.29 as you
pointed out.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-22 06:37:50 CEST

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.