Paul Hammant wrote on Tue, Oct 11, 2016 at 20:14:02 -0400: > > > I've read the ?kw=1 section of the release notes. My use case would not > > > need keyword replacement. In fact it would need it to be off. > > > > Are you sure? The only situations in which you'd need keywords > > expansion *off* is if your files *do* have svn:keywords set, but you > > used neither 'svn export' nor 'svn checkout' to extract the tree in the > > first place. > > > > Files will come up and down to Svn with curl (not the svn client). > I'm taking advantage of auto-versioning (SVNAutoversioning == on). > They'll be binary, and potentially large too - movie sized. Definitely > need keyword expansion to be off.
Keyword expansion is an opt-in feature. Subversion defaults to treating file contents as opaque binary blobs to be preserved verbatim. Anyway, in your situation, keywords aren't and won't be a factor. Consequently you can use the server's precomputed checksum of the content, which makes the implementation an order of magnitude easier. > As a test, I'm using openssl to make huge files that > change wholly with every revision, and trying to find the top limits of > Subversion. Sadly I've only found the top limits of Docker on the mac so > far - 60GB. 60GB being the size of each revision of a single versioned file? Daniel
