I've had sporadic trouble accessing the Code::Blocks sources via
https:// before.
svn+ssh:// works reliably without any problems whatsoever.
I use
svn+ssh://thomasdenk@svn.berlios.de/svnroot/repos/codeblocks/trunk/src for Code::Blocks.
My Subversion config file looks like this:
[tunnels]
ssh = C:/tools/plink.exe
[miscellany]
global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* *.gch *.layout *.depend *.cbCache *.res *.save
use-commit-times = yes
enable-auto-props = yes
### file-name-pattern = propname[=value][;propname[=value]...]
### The file-name-pattern can contain wildcards (such as '*' and
### '?'). All entries which match will be applied to the file.
[auto-props]
*.c = svn:eol-style=native;svn:keywords=Date Revision Author HeadURL Id
*.cpp = svn:eol-style=native;svn:keywords=Date Revision Author HeadURL Id
*.h = svn:eol-style=native;svn:keywords=Date Revision Author HeadURL Id
*.php = svn:keywords=Date Revision Author HeadURL Id
*.html = svn:keywords=Date Revision Author HeadURL Id
*.dsp = svn:eol-style=CRLF
*.dsw = svn:eol-style=CRLF
*.sh = svn:eol-style=native;svn:executable
*.txt = svn:eol-style=native
*.png = svn:mime-type=image/png
*.jp?g = svn:mime-type=image/jpeg
Makefile = svn:eol-style=native
Note the
[tunnels] section, and remember that the Subversion config file
does not like backslashes. Put in whatever ssh client you intend to use there, but abstain from backslashes.