From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: problem fetching the moduleh tree
Date: Thu, 13 Oct 2011 23:20:52 -0400 [thread overview]
Message-ID: <20111014032052.GD28189@windriver.com> (raw)
In-Reply-To: <20111014095826.cf6c8f622e411dff5d04d187@canb.auug.org.au>
[linux-next: problem fetching the moduleh tree] On 14/10/2011 (Fri 09:58) Stephen Rothwell wrote:
> Hi Paul,
>
> when trying to fetch the moduleh tree
> (git://openlinux.windriver.com/people/paulg/linux-next#for-sfr) today, I
> get a connection to the server, but it just hangs after that. I will use
> what I have from yesterday.
I'm seeing the same thing -- I've put in a service request and will get
folks to get it fixed up. Sorry about that.
Yesterday's will be fine -- it was just going to be the integration of
the conflict (deleted files) cleanups based on what you'd reported for
the Oct13 tree.
Paul.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
WARNING: multiple messages have this Message-ID (diff)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: problem fetching the moduleh tree
Date: Thu, 13 Oct 2011 23:20:52 -0400 [thread overview]
Message-ID: <20111014032052.GD28189@windriver.com> (raw)
In-Reply-To: <20111014095826.cf6c8f622e411dff5d04d187@canb.auug.org.au>
[linux-next: problem fetching the moduleh tree] On 14/10/2011 (Fri 09:58) Stephen Rothwell wrote:
> Hi Paul,
>
> when trying to fetch the moduleh tree
> (git://openlinux.windriver.com/people/paulg/linux-next#for-sfr) today, I
> get a connection to the server, but it just hangs after that. I will use
> what I have from yesterday.
I'm seeing the same thing -- I've put in a service request and will get
folks to get it fixed up. Sorry about that.
Yesterday's will be fine -- it was just going to be the integration of
the conflict (deleted files) cleanups based on what you'd reported for
the Oct13 tree.
Paul.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
next prev parent reply other threads:[~2011-10-14 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 22:58 linux-next: problem fetching the moduleh tree Stephen Rothwell
2011-10-14 3:20 ` Paul Gortmaker [this message]
2011-10-14 3:20 ` Paul Gortmaker
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=20111014032052.GD28189@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.