From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: failed to fetch the osd tree
Date: Sat, 13 Apr 2013 11:58:17 +1000 [thread overview]
Message-ID: <20130413115817.d1d0e711328ccb38bc387b04@canb.auug.org.au> (raw)
In-Reply-To: <5167A4E5.8060700@panasas.com>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Hi Boaz,
On Fri, 12 Apr 2013 09:08:37 +0300 Boaz Harrosh <bharrosh@panasas.com> wrote:
>
> That old server has finally crapped out on me.
> It is being replaced by a new machine. It will take few days
> to set up and run.
>
> So expect failure for the next few days
OK, I will ignore the errors for a while longer.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-04-13 1:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 23:17 linux-next: failed to fetch the osd tree Stephen Rothwell
2013-04-10 23:43 ` Stephen Rothwell
2013-04-12 6:08 ` Boaz Harrosh
2013-04-13 1:58 ` Stephen Rothwell [this message]
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=20130413115817.d1d0e711328ccb38bc387b04@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).