Nathan Hartman wrote: > Suggestion: The user provides the earliest SVN version with which they > want compatibility, and SVN picks the latest WC format version that is > compatible with it. [...]
And Daniel Sahlberg wrote: >> Regarding how to handle --wc-format-version=1.9, I'm leaning towards >> "use the newest format that was known by 1.9". That would enable a >> use case where I check the version of "the other svn client" (maybe >> an IDE integrated client), find that it is X.Y and then just use that >> version number instead of having to find out when the wc format of >> X.Y was actually introduced. Daniel and Nathan: That's what the current implementation does. It sounds rational by itself, but I pointed out some problems. That rule is not immediately obvious when, for example, a naïve user sees '--compatible-version=1.15' in a script. And (more so because) it is not consistent with the format that svn 1.15 chooses as its default format for creating working copies. By default it chooses 1.8 format (f31), not 1.15 format (f32). Your views on that would be good to hear. - Julian
