From: Jim Meyering <jim@meyering.net>
To: Diego Novillo <dnovillo@google.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Getting connection reset messages on git operations
Date: Wed, 28 Mar 2012 16:25:00 -0000 [thread overview]
Message-ID: <87398su204.fsf@rho.meyering.net> (raw)
In-Reply-To: <4F733AB4.7050007@google.com> (Diego Novillo's message of "Wed, 28 Mar 2012 12:22:12 -0400")
Diego Novillo wrote:
> $ git svn info
> Path: .
> URL: svn+ssh://gcc.gnu.org/svn/gcc/trunk
> Repository Root: svn+ssh://gcc.gnu.org/svn/gcc
> Repository UUID: 138bc75d-0d04-0410-961f-82ee72b054a4
> Revision: 184830
> Node Kind: directory
> Schedule: normal
> Last Changed Author: dnovillo
> Last Changed Rev: 184830
> Last Changed Date: 2012-03-02 16:30:11 -0500 (Fri, 02 Mar 2012)
>
> $ git pull
> fatal: read error: Connection reset by peer
>
> I'm not getting the same errors doing SVN operations.
Perhaps related: today I noticed something odd:
updating an old binutils clone, it took something like 15 minutes.
That was an hour or two ago.
next prev parent reply other threads:[~2012-03-28 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 16:22 Diego Novillo
2012-03-28 16:25 ` Jim Meyering [this message]
2012-03-28 16:32 ` Frank Ch. Eigler
2012-03-28 16:35 ` Diego Novillo
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=87398su204.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=dnovillo@google.com \
--cc=overseers@gcc.gnu.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).