From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: is orgmode.org's git repo down? Date: Sat, 23 Jan 2016 09:06:46 -0500 Message-ID: <877fj0gzk9.fsf@pierrot.dokosmarshall.org> References: <877fj11ldz.fsf@alphaville.usersys.redhat.com> <20160122222032.3b856f0b@lt70.mpip-mainz.mpg.de> <8737tp1c59.fsf@alphaville.usersys.redhat.com> <20160123102453.1810991a@lt70.mpip-mainz.mpg.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42615) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMyqC-0000z4-7h for emacs-orgmode@gnu.org; Sat, 23 Jan 2016 09:07:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMyq7-0001e9-90 for emacs-orgmode@gnu.org; Sat, 23 Jan 2016 09:07:00 -0500 Received: from plane.gmane.org ([80.91.229.3]:58783) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMyq7-0001dD-2G for emacs-orgmode@gnu.org; Sat, 23 Jan 2016 09:06:55 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aMyq5-0007xR-RY for emacs-orgmode@gnu.org; Sat, 23 Jan 2016 15:06:54 +0100 Received: from pool-74-104-158-160.bstnma.fios.verizon.net ([74.104.158.160]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 Jan 2016 15:06:53 +0100 Received: from ndokos by pool-74-104-158-160.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 Jan 2016 15:06:53 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org "Robert H. Klein" writes: > Hi, > > On Fri, 22 Jan 2016 17:55:13 -0500 > Gary Oberbrunner wrote: > >> Restarting didn't make git: work, but now http: does. Thanks! > > Yes, the git protocol uses another server program 'git-daemon', not the > web server. > > Anyway, I found a configuration glitch and now it works again. > Indeed it does - thanks! -- Nick