2008/6/8 Mark Phippard <markphip_at_gmail.com>:
> November 2007. I am assuming this bug impacts SVK, since clkao
> reported it and I have seen some other talk of segfaults from SVK
> users. Does this mean that no one has tried SVK with 1.5 code until
> the last week? If that is true, are we saying they cannot wait until
> 1.5.1? I've been testing the Java API daily since last summer.
FTR, this does not cause SVK regression unless you have a start-commit
hook, which usually isn't the case. And the problem was found when
testing the SVN::Hook module which isn't really widely used. One of
its regression test happens to use the start-commit hook and caused
segfault.
From the point of API consumers we'd just tell users about the
incompatibility in the given condition (ie 1.5.0 and the start-commit
hook) in case this does not get in. I do personally want to see the
release as well, and I'd say this is rather a minor impact for the
projects using the API that I know about.
Cheers,
CLK
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-09 09:50:31 CEST