From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: unable to fetch the watchdog tree
Date: Fri, 24 Mar 2017 09:13:22 +1100 [thread overview]
Message-ID: <20170324091322.55edcbe5@canb.auug.org.au> (raw)
In-Reply-To: <20161205093934.4d5449fa@canb.auug.org.au>
Hi Wim,
On Mon, 5 Dec 2016 09:39:34 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Tue, 22 Nov 2016 09:49:19 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Mon, 14 Nov 2016 16:26:16 +0100 Wim Van Sebroeck <wim@iguana.be> wrote:
> > >
> > > This has been fixed. Thanks for notifying me about it.
> > >
> > > > For the past few days (nearly a week, sorry) fetching the watchdog tree
> > > > (git://www.linux-watchdog.org/linux-watchdog-next.git#master) has
> > > > resulted in a hung connection.
> >
> > It's happening again :-(
>
> And again. Have you considered moving your tree somewhere more
> reliable like kernel.org?
And again. It connects and then just hangs :-(
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-03-23 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 22:34 linux-next: unable to fetch the watchdog tree Stephen Rothwell
2016-11-14 15:26 ` Wim Van Sebroeck
2016-11-21 22:49 ` Stephen Rothwell
2016-12-04 22:39 ` Stephen Rothwell
2016-12-04 22:47 ` Ozgur Karatas
2016-12-05 10:17 ` Wim Van Sebroeck
2017-03-23 22:13 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-07 0:12 Stephen Rothwell
2013-05-07 20:29 ` Wim Van Sebroeck
2012-05-21 23:16 Stephen Rothwell
2012-05-22 15:29 ` Wim Van Sebroeck
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=20170324091322.55edcbe5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=wim@iguana.be \
/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).