From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: git question
Date: Tue, 28 Feb 2006 15:45:10 +0000 [thread overview]
Message-ID: <44047006.9030204@sgi.com> (raw)
In-Reply-To: <yq08xsez26a.fsf@jaguar.mkp.net>
Luck, Tony wrote:
>>Another git issue:
>>
>>[jes@tomahawk linux-2.6]$ git-pull
>>fatal: read error (Connection reset by peer)
>>Fetch failure: git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git
>>
>>Anyone seen that one before? Worked last week.
>
>
> Not my fault (this time). I haven't pushed anything up to kernel.org
> (or made any other repo changes) since Feb 18th. The version of git
> on kernel.org was updated to 1.2.3 on Feb 23rd. What date was your last
> good pull?
Hmm I wonder if thats it. I had a good pull on Thursday for sure, but
I think I did on Friday as well. Someone else reported problems against
other repos.
It seems that if one keeps retrying, eventually it will work, but it
seems very random.
Cheers,
Jes
next prev parent reply other threads:[~2006-02-28 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 10:04 git question Jes Sorensen
2006-02-14 13:12 ` Jes Sorensen
2006-02-14 16:56 ` Luck, Tony
2006-02-28 9:51 ` Jes Sorensen
2006-02-28 15:22 ` Luck, Tony
2006-02-28 15:45 ` Jes Sorensen [this message]
2006-02-28 15:51 ` Luck, Tony
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=44047006.9030204@sgi.com \
--to=jes@sgi.com \
--cc=linux-ia64@vger.kernel.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