All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS list <linux-nfs@vger.kernel.org>,
	Benny Halevy <bhalevy@panasas.com>,
	"J. Bruce Fields" <bfields@citi.umich.edu>
Subject: Re: Problems with the git://linux-nfs.org/ server
Date: Tue, 28 Sep 2010 15:32:51 +0200	[thread overview]
Message-ID: <4CA1EE83.1000700@panasas.com> (raw)
In-Reply-To: <1285679386.9185.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

On 09/28/2010 03:09 PM, Trond Myklebust wrote:
> On Tue, 2010-09-28 at 11:23 +0200, Boaz Harrosh wrote:
>> It looks like the git daemon on git://linux-nfs.org/ is down
>>
>> Thanks
>> Boaz
> 
> It's working for me...
> 
> [trondmy@heimdal linux-2.6]$ git remote update linux-nfs
> Fetching linux-nfs
> 
> Cheers
>   Trond
> 

Thanks. I still get problems so I guess it's related to
this side of the ocean, I'm trying for example:

$ git ls-remote git://git.linux-nfs.org/~trondmy/nfs-2.6.git
And get: git.linux-nfs.org[0: 173.201.45.137]: errno=Connection timed out

But ping git.linux-nfs.org works (8% packet loss)

I'll wait for things to calm down, I guess

Boaz



  parent reply	other threads:[~2010-09-28 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28  9:23 Problems with the git://linux-nfs.org/ server Boaz Harrosh
2010-09-28 13:09 ` Trond Myklebust
     [not found]   ` <1285679386.9185.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-09-28 13:32     ` Boaz Harrosh [this message]
2010-09-28 13:49       ` Trond Myklebust
     [not found]         ` <1285681777.9185.13.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-09-28 14:47           ` Benny Halevy
2010-09-28 14:50             ` Benny Halevy

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=4CA1EE83.1000700@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=bfields@citi.umich.edu \
    --cc=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --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 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.