On 27.11.2013 19:57, Philip Martin wrote: > SVNAutoversioning involves single requests, like PUT or MKCOL, that > create a new revision by creating, populating and committing a > transaction. These requests cannot use the new scheme above because > there is no way to pass the date, it is difficult to modify the request > body and it is not possible to send a separate PROPPATCH request.
You should just ignore autoversioning. Sure, you can't change the date on the transaction created and committed that way, but you don't have to: we're talking about replicating the revision (including it's svn:date property) /after/ it has been committed, and I don't see why you'd want to do that by replaying the actual autoversioning HTTP/DAV request. Svnsync shouldn't care how the revision was created, it doesn't even have to sync using HTTP. And, since you mentioned WANdisco, neither should their replicator. IIRC, the only way to distinguish an autoversioning commit from any other commit after the fact is by looking at the log message (and hoping that someone didn't fake it). -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
