Yes, I noticed that and sent a mail to [EMAIL PROTECTED]
You can workaround by relocating the working copy to use http:// instead, as in: svn switch --relocate svn://gcc.gnu.org/svn/gcc/trunk http://gcc.gnu.org/svn/gcc/trunk On 13/09/06, Jack Howarth <[EMAIL PROTECTED]> wrote:
Has anyone else had problems accessing the svn server today for gcc? I tried from home and work today. In both cases, the 'svn update' never produces any updates of new files or completes. Jack