From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Schindelin Subject: Re: cant get git to work over http Date: Tue, 19 Feb 2008 22:20:24 +0000 (GMT) Message-ID: References: <47BB3691.9040809@freescale.com> <47BB5037.5090302@freescale.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Jon Loeliger , Mike Hommey , git@vger.kernel.org To: Anatoly Yakovenko X-From: git-owner@vger.kernel.org Tue Feb 19 23:21:36 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 1JRaq0-00080f-1a for gcvg-git-2@gmane.org; Tue, 19 Feb 2008 23:21:20 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755146AbYBSWUk (ORCPT ); Tue, 19 Feb 2008 17:20:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755511AbYBSWUk (ORCPT ); Tue, 19 Feb 2008 17:20:40 -0500 Received: from mail.gmx.net ([213.165.64.20]:36540 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754673AbYBSWUj (ORCPT ); Tue, 19 Feb 2008 17:20:39 -0500 Received: (qmail invoked by alias); 19 Feb 2008 22:20:37 -0000 Received: from unknown (EHLO [138.251.11.74]) [138.251.11.74] by mail.gmx.net (mp018) with SMTP; 19 Feb 2008 23:20:37 +0100 X-Authenticated: #1490710 X-Provags-ID: V01U2FsdGVkX1+oYWQQWAeoiT2xvk1+MNwWz1e7mjBPuKI7thVgoX 1pmWtuWv0U4pye X-X-Sender: gene099@racer.site In-Reply-To: User-Agent: Alpine 1.00 (LSU 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, 19 Feb 2008, Anatoly Yakovenko wrote: > On Feb 19, 2008 1:59 PM, Anatoly Yakovenko wrote: > > > Something is fishy here. Is your repository bare or not? > > > > no, why does it need to be bare? > > > so bare or not ssh works but http doesnt: Having a non-bare repository on a web server does not make sense at all. It's not like you will be developing in there, right? And yes, you can append "/.git/" to your URL and it should work fine. HTTP transport is a second class citizen, and will probably never be as efficient as GIT transport. Therefore, you can choose to continue your efforts with the http:// URL, but are mostly on your own, or you can go with ssh (git://) and it just works. Unfortunately, I do not have the time to help you more. Ciao, Dscho