"Sergey A. Lipnevich" <sergey@optimaltec.com> writes:
> 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).
Ah! Heh, sorry, I didn't need to post this, I guess:
> Sergey, if you want to merge just so you can get a clean
> rebranch, that's fine. Just make sure that the 0.24 side gets
> disabled somehow (in the configury check maybe?), so that trunk
> Subversion remains formally incompatible with Neon 0.24. This
> way will be least confusing for users.
Should have read all your mails before replying.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 12 17:58:35 2003