http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate
"The Subversion repository dump format describes versioned repository changes
only. It will not carry any information about uncommitted transactions, user
locks on filesystem paths, repository or server con
Designation: Non-SSA/Finmeccanica
Daniel Shahaf wrote:
> Yeah, but you do that in three round-trips rather than two:
>
> GET /foo//bar//baz
> 301 Moved Permanently
> Location: /foo/bar//baz
> GET /foo/bar//baz
> 301 Moved Permanently
> Location: /foo/bar//baz
> GET /foo/bar/baz
> 200 OK
Right,
Designation: Non-SSA/Finmeccanica
Daniel Shahaf wrote:
> Sure, knowing exactly what build you used is relevant information.
>
> It's just the adjective "official" that caught my eye.
Thank you for clearing up that bit of minutia.
>> That's a solution much like cutting off a finger to get rid
Designation: Non-SSA/Finmeccanica
Daniel Shahaf wrote:
> The Apache Subversion Project does not release binaries, official or
> otherwise. CollabNet, Inc. is > one of several third parties who build and
> release binaries of our software.
Just letting everyone know what binaries I was usin
Designation: Non-SSA/Finmeccanica
I was having problems performing a commit on a slave server using a 1.6.17
client, but not when using the newer 1.7.x client. This started occurring when
I upgraded from the latest 1.6.x server to the 1.7.1 using the official
Collabnet binaries on Linux. (I
