I flipped *back* to Python's requests.put(..) in my solution - from a regular Svn client. That relies on 'autoversioning=on' for it to work over DAV, I mean. In that configuration it functions like curl, of course.
*Commit Messages* I'd love a --header "svn:message: my message" too. I raised it before in https://issues.apache.org/jira/browse/SVN-4454 but the team was split back in 2013 on yes vs no. I'm thinking I'd like it again, having reviewed all the comments. Can I ask for that issue/request to be reopened, please ? *An Aside* My CMS thing from 11 years ago used SeaMonkey (or MsWord2004 (not sure of the year) before Microsoft killed DAV support in Office) for a vanilla 'PUT' of a page. I would have needed to have contributed to *SeaMonkey's* codebase to have an inline *commit message* added to the 'publish' dialog box for the page editor. The code's in GitHub these days if anyone is interested, as all of Codehaus' repos were copied there before shutdown of that fondly remembered portal. Codehaus being the first OSS code portal to provision Subversion (pre 1.0). On Wed, Jul 12, 2017 at 5:45 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Wed, Jul 12, 2017 at 10:40 PM, Paul Hammant <p...@hammant.org> wrote: > > I'd be fine with that too if it is also settable via curl --header > > "svn:compression: no" for non-client auto-increment operations. > > I'm wondering whether you'll still need this. You ended up with > curl+autoversioning (at Philip's suggestion) because that eliminates > the client-side deltification and compression overhead. But if the > normal svn client grows support to skip those (with the svn: property > Mark pointed to, or through some other technique), you might be able > to use a normal client with the same (or very close) performance as > curl+autoversioning. > > -- > Johan >
