From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Schindelin Subject: Re: git-clone works with ssh but not with http/https/git Date: Tue, 24 Jun 2008 12:48:19 +0100 (BST) Message-ID: References: <1214306517.6441.10.camel@localhost> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Matthias Kestenholz , git@vger.kernel.org To: Erez Zilber X-From: git-owner@vger.kernel.org Tue Jun 24 13:51:33 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1KB73U-00022o-V3 for gcvg-git-2@gmane.org; Tue, 24 Jun 2008 13:51:25 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753935AbYFXLuY (ORCPT ); Tue, 24 Jun 2008 07:50:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751692AbYFXLuY (ORCPT ); Tue, 24 Jun 2008 07:50:24 -0400 Received: from mail.gmx.net ([213.165.64.20]:44275 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753365AbYFXLuX (ORCPT ); Tue, 24 Jun 2008 07:50:23 -0400 Received: (qmail invoked by alias); 24 Jun 2008 11:50:21 -0000 Received: from almond.st-and.ac.uk (EHLO almond.st-and.ac.uk) [138.251.155.241] by mail.gmx.net (mp055) with SMTP; 24 Jun 2008 13:50:21 +0200 X-Authenticated: #1490710 X-Provags-ID: V01U2FsdGVkX1+qi1RQQPeqlxKnRx9oL77nmuv/IzS4tzI4HYfKoq eFepmkyArdGtp4 X-X-Sender: gene099@racer In-Reply-To: User-Agent: Alpine 1.00 (DEB 882 2007-12-20) X-Y-GMX-Trusted: 0 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Hi, On Tue, 24 Jun 2008, Erez Zilber wrote: > On Tue, Jun 24, 2008 at 2:21 PM, Matthias Kestenholz wrote: > > On Tue, 2008-06-24 at 14:15 +0300, Erez Zilber wrote: > > > >> [root@kd001 t]# git-clone http://kites/pub/git/erez.zilber/my_test.git > >> Initialized empty Git repository in /home/erez.zilber/work/tmp/t/my_test/.git/ > >> Cannot get remote repository information. > >> Perhaps git-update-server-info needs to be run there? > >> > > > > Maybe you should run git-update-server-info in the repository on the > > server? > > Forgot to mention - I tried to run git-update-server-info from the > repository on the server. No, you did not. Otherwise, the message would not appear. It can be that you have _another_ repository on the server, but running update-server-info there does not help. > I got the same results. BTW - if it works OK with ssh, I can only guess > that git-update-server-info won't help for http. right? Wrong again. ssh transport is special, and does not need the information update-server-info provides. Hth, Dscho