Ben Collins-Sussman wrote:
>>If all the tests pass, +1 on merging. You do the honors :-) (your
>>commit access will work fine, there's no automated restriction on the
>>server, just human convention).
>Do we really want to merge the neon-0.24 branch just yet? David Waite
>still has a ton of SSL changes to make. If we merge the branch now,
>then it's possible someone will casually link HEAD svn against
>neon-0.24, and bam, the cert stuff either won't compile or won't run.
No, no! I'm not going to get build/* files changes in, just ra_dav. The
way it's done right now, the brunt of the change is to replace many
identifiers and introduce some bridging code, and do Neon 0.24 support
within #defines which will only be activated with newer Neon (which is
not going to happen because of build check doesn't change). Hence, the
current logic stays intact, Neon 0.24 is not supported on the trunk, and
subsequent merges become easier.
I'm almost done with file:// tests, http:// will be next, than I merge
the subversion/* part, and then merge trunk back into branch (after
finding out what revision the branch was made in).
Received on Fri Aug 22 03:59:43 2003