public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: overseers@sourceware.org
Subject: FW: svn+ssh connection times out (fwd)
Date: Thu, 30 Aug 2012 10:40:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1208300630290.86705@dair.pair.com> (raw)

Not sure what *I* am asked to do (or why I was picked), unless
it's forwarding a message that bounced (perhaps due to the
connection failure) when trying to address the list directly.

---------- Forwarded message ----------
Date: Thu, 30 Aug 2012 03:04:57
From: "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Subject: FW: svn+ssh connection times out

Hi H-P,

Can you please have a look at this issue.

IT people say that traffic is dropping from the other end.  They say AMD NAT 202.56.249.162 added to Access control list in gcc.gnu.org will solve the issue.

-----Original Message-----
From: Kumar, Venkataramanan
Sent: Monday, August 27, 2012 12:00 PM
To: 'overseers@gcc.gnu.org'
Subject: svn+ssh connection times out

Hi,

My account name: vekumar@gcc.gnu.org

I have Write after approval access for the gcc repository.

I am trying to checkout gcc repository using svn+ssh from Bangalore (India).

> svn co svn+ssh://vekumar@gcc.gnu.org/svn/gcc/trunk gcc

Read from socket failed: Connection timed out
svn: Connection closed unexpectedly

I checked with our IT people. They say that gcc.gnu.org site is not allowing the Bangalore office traffic.

Please suggest a way to solve this.

Regards,
Venkat.


             reply	other threads:[~2012-08-30 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 10:40 Hans-Peter Nilsson [this message]
2012-08-30 18:49 ` Jonathan Larmour
2012-08-30 20:26   ` Frank Ch. Eigler
2012-08-30 21:19   ` Matthew Galgoci

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.BSF.2.00.1208300630290.86705@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).