Re: 1.7 write-through proxy to 1.6 master

"C. Michael Pilato" <cmpilato_at_collab.net> writes:

> Another less-obvious one was with the introduction of merge
> tracking, where the repository format version dictated support (or lack
> thereof) for a client-visible feature. You might have had an existing 1.4
> server (no merge tracking), popped up a 1.5 slave when that feature was
> released, and now the clients are told that the server supports merge
> tracking when it actually doesn't.

Does that matter? The slave replies to all read requests from its own
repository, and that does support mergeinfo. Only write requests in a
commit go through to the master and its repository. Are there any write
requests that depend on the server's support for mergeinfo?

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com