From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31004 invoked by alias); 5 Jan 2017 17:26:16 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 30975 invoked by uid 89); 5 Jan 2017 17:26:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=H*M:stream X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 05 Jan 2017 17:26:05 +0000 Date: Thu, 05 Jan 2017 17:26:00 -0000 From: Mark Wielaard To: "Frank Ch. Eigler" Cc: "Frank Ch. Eigler" , overseers@sourceware.org Subject: Re: git through http (or https) Message-ID: <20170105172528.GA11878@stream> References: <20170103212227.GK2187@stream> <20170103234052.GD412@elastic.org> <20170104124301.GL2187@stream> <20170105160316.GA23594@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170105160316.GA23594@redhat.com> User-Agent: Mutt/1.7.1 (2016-10-04) X-Spam-Score: -2.9 (--) X-SW-Source: 2017-q1/txt/msg00008.txt.bz2 Hi Frank, On Thu, Jan 05, 2017 at 11:03:16AM -0500, Frank Ch. Eigler wrote: > > [...] Also directly viewing https://sourceware.org/git/elfutils.git > > still doesn't work [...] > > None of the sourceware git repos serve that URL straight to web > browsers. Try instead: > https://sourceware.org/git/ > https://sourceware.org/git/?p=elfutils.git;a=summary Yes, that is what the rewrite rules would fix. If you enable the rules in htdocs/git/.htaccess then you can view the repository using more human readable/discoverable links. So if you could do that, that would be appreciated. That is how fedorahosted is also setup (like most git web URLS). The main issue is that the git clone URL currently forwards to the underlying directory which then gives a Forbidden page. That is just confusing. Even if you don't want nicer URLs for viewing then having the main git clone URL actually work (might just forward for the ?p=repo.git page) would at least not make it look like the repository is not there/broken. If you like, and trust me with admin access, I can also come up and experiment with the rewrite rules for the .htaccess file myself. Thanks, Mark