.I'm not on the list and couldn't find this in archive search...please cc
me on any responses...thx!
Was going to report this error over at the TortoiseSVN site, but apparently
they are pointing over here. Here's the link to the discussion over on
Tortoise:
http://tortoisesvn.tigris.org/ds/viewMe
This quite resembles an issue reported last week which is intended to be
fixed in serf 1.2.2. It's possible you could upgrade just your serf
libraries, not svn as well (though, since you likely use a binary
package, just upgrading to svn 1.8.1 packages that include serf 1.2.2
might be easiest).
S
How would one upgrade to svn 1.8.1 as it exists within TortoiseSVN?
That is, I simply run TortoiseSVN, check stuff in and out of my unfuddle
repository, and am deliberately and blissfully unaware of all the
machinations that happen when I right click in Explorer and choose "SVN
Commit". For exampl
Guten Tag Dave Steckler,
am Dienstag, 25. Juni 2013 um 00:35 schrieben Sie:
> How would one upgrade to svn 1.8.1 as it exists within TortoiseSVN?
> [...]For example, I have no idea what "serf",
> amongst all the libraries used by svn, even is.
Simply wait for the next release of TortoiseSVN or d
I think this is another instance of a proxy not supporting chunked
Transfer-Encoding. For a commit to a 1.7 server the client sends a
chunked POST, the proxy responds with a 411, and the client shows the
error. For a commit to a 1.6 server the client sends a chunked
PROPFIND, the proxy responds wi
> How would one upgrade to svn 1.8.1 as it exists within TortoiseSVN?
Simply look at the name of the TSVN download file... the current download is:
TortoiseSVN-1.8.0.24401-x64-svn-1.8.0
This has two version numbers in it. The first is the TSVN version number,
1.8.0.24401.
The second is the ver
