On Mon Dec 03 16:36:40 2007, [EMAIL PROTECTED] wrote: > Yes, up upgrading svn does it. ....
> Unless somebody wants to add a patch to check for > svn versions, you can close this one as of my account. > I do *not* want to add a patch to check for svn versions. lib/Parrot/Revision.pm is already enough of a mindf*!#$k and I do not want it to get any more complex and unmaintainable than it already is. Plus, if we opened the door to checking for svn versions, eventually we'd be checking for svk versions and git versions as well. And then only an expert in all 3 VCSes would be qualified to maintain Parrot::Revision. So I'm going to close this ticket. Since 'make smoke' is something that is likely to be done only by a small but relatively sophisticated group of hackers, I think we'll be able to include a recommendation to them to upgrade to Subversion 1.44 (?) before smoke testing and be confident that they'll get it right. kid51
