julianfoad_at_apache.org wrote on Mon, Feb 20, 2012 at 18:20:39 -0000:
> Author: julianfoad
> Date: Mon Feb 20 18:20:39 2012
> New Revision: 1291397
>
> URL: http://svn.apache.org/viewvc?rev=1291397&view=rev
> Log:
> * STATUS: Cast a vote.
>
> Modified:
> subversion/branches/1.7.x/STATUS
>
> Modified: subversion/branches/1.7.x/STATUS
> URL: http://svn.apache.org/viewvc/subversion/branches/1.7.x/STATUS?rev=1291397&r1=1291396&r2=1291397&view=diff
> ==============================================================================
> --- subversion/branches/1.7.x/STATUS (original)
> +++ subversion/branches/1.7.x/STATUS Mon Feb 20 18:20:39 2012
> @@ -94,7 +94,7 @@ Candidate changes:
> r1244303 and r1244317 add a test.
> r1245284 and r1245285 implement a fix.
> Votes:
> - +1: stsp
> + +1: stsp, julianfoad
>
Julian -- wrt your IRC question about r1244303 -- no, I don't know why
adding an 'update' to the test does or doesn't avoid the bug on the
branch.
The comment merely records the fact that (on trunk) when the .py test
contained an 'svn up SUBDIR' statement[1] at that location, it XPassed;
dropping that 'up' (which the .sh script I was porting doesn't have)
made the test XFail. I have not looked into the bug itself.
[1] I think it was an 'svn up A_COPY' statement¸ as the preceding thing
the test does is commit a child of A_COPY.
> * r1245738, r1245817
> Say "sqlite:" in front of SQLite's error messages.
>
>
Received on 2012-02-20 22:45:54 CET