From: Ozgur Karatas <ozgur@member.fsf.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Wim Van Sebroeck <wim@iguana.be>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: unable to fetch the watchdog tree
Date: Mon, 05 Dec 2016 00:47:12 +0200 [thread overview]
Message-ID: <2586391480891632@web26h.yandex.ru> (raw)
In-Reply-To: <20161205093934.4d5449fa@canb.auug.org.au>
Hello all,
I get a error last week and I couldn't connect from below url:
http://www.linux-watchdog.org/cgi-bin/gitweb.cgi?p=linux-watchdog.git;a=summary
http://www.linux-watchdog.org/cgi-bin/gitweb.cgi?p=linux-watchdog-next.git;a=summary
why do not you use GitHub?
Regards,
Ozgur
05.12.2016, 00:40, "Stephen Rothwell" <sfr@canb.auug.org.au>:
> Hi Wim,
>
> 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?
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2016-12-04 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 22:34 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 [this message]
2016-12-05 10:17 ` Wim Van Sebroeck
2017-03-23 22:13 ` Stephen Rothwell
-- 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=2586391480891632@web26h.yandex.ru \
--to=ozgur@member.fsf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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
all inboxes | Powered by JetHome®