From: Joe Perches <joe@perches.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Boaz Harrosh <ooo@electrozaur.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error when fetching the osd tree
Date: Thu, 06 Aug 2015 18:24:07 -0700 [thread overview]
Message-ID: <1438910647.2322.4.camel@perches.com> (raw)
In-Reply-To: <20150807090104.0d54f11f@canb.auug.org.au>
On Fri, 2015-08-07 at 09:01 +1000, Stephen Rothwell wrote:
> Hi Boaz,
>
> Fetching the osd tree
> (git://git.open-osd.org/linux-open-osd.git#linux-next) for the past few
> days has produced this error:
>
> connection reset by peer
And mail sent to osd-dev@open-osd.org gets:
Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn more
at https://support.google.com/mail/answer/7720
[(0) cyclone.open-osd.org. [209.166.131.141]:25: socket error]
next prev parent reply other threads:[~2015-08-07 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 23:01 linux-next: error when fetching the osd tree Stephen Rothwell
2015-08-07 1:24 ` Joe Perches [this message]
2015-08-10 8:23 ` Boaz Harrosh
2015-08-10 22:53 ` Stephen Rothwell
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=1438910647.2322.4.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ooo@electrozaur.com \
--cc=sfr@canb.auug.org.au \
/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