You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by Daniel Shahaf <d....@daniel.shahaf.name> on 2012/10/14 19:22:02 UTC
Re: svn commit: r1397993 -
/subversion/branches/http-dynamic-prop-namespaces/BRANCH-README
cmpilato@apache.org wrote on Sun, Oct 14, 2012 at 01:44:59 -0000:
> Author: cmpilato
> Date: Sun Oct 14 01:44:59 2012
> New Revision: 1397993
>
> URL: http://svn.apache.org/viewvc?rev=1397993&view=rev
> Log:
> On the 'http-dynamic-prop-namespaces' branch: update BRANCH-README.
>
> Modified:
> subversion/branches/http-dynamic-prop-namespaces/BRANCH-README
>
> Modified: subversion/branches/http-dynamic-prop-namespaces/BRANCH-README
> URL: http://svn.apache.org/viewvc/subversion/branches/http-dynamic-prop-namespaces/BRANCH-README?rev=1397993&r1=1397992&r2=1397993&view=diff
> ==============================================================================
> --- subversion/branches/http-dynamic-prop-namespaces/BRANCH-README (original)
> +++ subversion/branches/http-dynamic-prop-namespaces/BRANCH-README Sun Oct 14 01:44:59 2012
> @@ -21,6 +21,12 @@ the suite does pass all tests now in the
> trunk client vs. branch server
> branch client vs. branch server
>
> +Note that Bert will probably suggest soon that there be a way to flip
> +off the server-side support for this to accomodate WebDAV proxy
> +configurations where the slave and master are of different pedigrees.
Do we actually support this? I remember a thread a few years ago
concluding that the master and slave had to be similar versions... (but
I don't recall whether "similar" was "same minor version" or "same patch
version")
> +*sigh*. Having to expose feature toggles of this sort to admins is
> +wrong on so many levels.
> +
>
> BACKGROUND INFORMATION
> ======================
>
>
Re: svn commit: r1397993 - /subversion/branches/http-dynamic-prop-namespaces/BRANCH-README
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 10/14/2012 01:22 PM, Daniel Shahaf wrote:
>> +Note that Bert will probably suggest soon that there be a way to flip
>> +off the server-side support for this to accomodate WebDAV proxy
>> +configurations where the slave and master are of different pedigrees.
>
> Do we actually support this? I remember a thread a few years ago
> concluding that the master and slave had to be similar versions... (but
> I don't recall whether "similar" was "same minor version" or "same patch
> version")
I recall the discussion, but recall the conclusion going the other way.
Hence, "SVNAdvertiseV2Protocol" remains in our httpd.conf directive set.
I've started another thread on this topic, so please pick up the discussion
there if you've something to add.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development
Re: svn commit: r1397993 - /subversion/branches/http-dynamic-prop-namespaces/BRANCH-README
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 10/14/2012 01:22 PM, Daniel Shahaf wrote:
>> +Note that Bert will probably suggest soon that there be a way to flip
>> +off the server-side support for this to accomodate WebDAV proxy
>> +configurations where the slave and master are of different pedigrees.
>
> Do we actually support this? I remember a thread a few years ago
> concluding that the master and slave had to be similar versions... (but
> I don't recall whether "similar" was "same minor version" or "same patch
> version")
I recall the discussion, but recall the conclusion going the other way.
Hence, "SVNAdvertiseV2Protocol" remains in our httpd.conf directive set.
I've started another thread on this topic, so please pick up the discussion
there if you've something to add.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development