Hi all,

There are a bunch of stuff in STATUS waiting for backport that I think
would be nice to have released. Following Stefan Sperling's excellent lead
during the last release I'd like to take a shot at it when the time comes.

I've spent the evening looking through the items and I'll send my notes
here hoping someone will pick up on it.

r1921264: The fix seems good. I'll try to merge it locally and vote for it.

r1921505 and r1921506: Need a backport branch (see separate e-mail [1]). I
guess I could cobble something together but I don't know what I'm doing so
I'd prefer if someone with more experience in the bindings could look at it.

r1921266 and r1921267: Seems simple enough but needs to be tested by
someone with a working win32 environment (I'm still struggling). @Johan
Corveleyn <jcor...@gmail.com> ?

r1921371: This is the test we've already used in the 1.14.4 release so it
should be simple enough to check.

Any volunteers to check the above?

I think I've managed to roll functional tarballs based on the current state
of the 1.14.x branch, but I did get an error:

[[[
WARNING:root:CHANGES has unmerged revisions: r1921179
]]]

As far as I can tell the actual changes were already merged and doing

~/svn_1.14.x$ svn merge -c1921179
https://svn.apache.org/repos/asf/subversion/trunk

only add 1921179 to the mergeinfo. Is this the correct action, ie should I
commit the updated mergeinfo?

Cheers,
Daniel


[1] https://lists.apache.org/thread/fbckfwy0lr61392t0v52x62fkfqmg38b

Reply via email to