linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-next@vger.kernel.org
Subject: Re: linux-next: unable to fetch the moduleh tree
Date: Thu, 2 Aug 2012 17:05:19 -0400	[thread overview]
Message-ID: <501AEB8F.10908@windriver.com> (raw)
In-Reply-To: <20120802085448.5fb877ce7747128ba354f605@canb.auug.org.au>

On 12-08-01 06:54 PM, Stephen Rothwell wrote:
> Hi Paul,
> 
> For the last few days, I have been getting this error when trying to
> fetch the moduleh tree:
> 
> fatal: unable to connect to openlinux.windriver.com:
> openlinux.windriver.com[0: 192.124.127.100]: errno=Connection timed out
> 
> Is this tree still in use?  Or should I just remove it from linux-next?

Hi Stephen,

Go ahead and remove it.  If/when I've something else that I can't
push via a maintainer tree, I'll get you to add one with a more
appropriate name, and serve it from kernel.org instead.

Thanks,
Paul.

> 

  reply	other threads:[~2012-08-02 21:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 22:54 linux-next: unable to fetch the moduleh tree Stephen Rothwell
2012-08-02 21:05 ` Paul Gortmaker [this message]
2012-08-02 23:03   ` 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=501AEB8F.10908@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).