From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: nfs/nfsd trees fetch failed
Date: Mon, 2 Nov 2009 15:15:18 -0500 [thread overview]
Message-ID: <20091102201518.GD19271@fieldses.org> (raw)
In-Reply-To: <20091102094151.3ad599a8.sfr@canb.auug.org.au>
On Mon, Nov 02, 2009 at 09:41:51AM +1100, Stephen Rothwell wrote:
> Hi Trond,
>
> On Sun, 01 Nov 2009 17:03:38 -0500 Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> >
> > Yes. It's a known problem: an upgrade+reboot that went awry combined
> > with a remote console failure. I'm hoping that Bruce might be able to
> > help out when he returns to the office tomorrow morning...
>
> OK, thanks.
It should be working now.
--b.
next prev parent reply other threads:[~2009-11-02 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 21:58 linux-next: nfs/nfsd trees fetch failed Stephen Rothwell
2009-11-01 22:03 ` Trond Myklebust
2009-11-01 22:41 ` Stephen Rothwell
2009-11-02 20:15 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-26 21:39 Stephen Rothwell
2009-11-26 22:30 ` Trond Myklebust
2009-11-26 22:59 ` 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=20091102201518.GD19271@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@fys.uio.no \
/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).