qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Jeff Cody" <jeff@codyprime.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] git.qemu.org gitweb misrenders on git/ URLs
Date: Mon, 2 Sep 2019 10:25:09 +0100	[thread overview]
Message-ID: <20190902092509.GC9069@stefanha-x1.localdomain> (raw)
In-Reply-To: <3fce8d5a5fcccbff8f27f681eb685167d2c0845f.camel@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]

On Thu, Aug 29, 2019 at 06:13:34PM +0200, Andrea Bolognani wrote:
> On Thu, 2019-08-29 at 16:48 +0100, Stefan Hajnoczi wrote:
> > Hi Jeff,
> > Philippe noticed that the git HTTPS clone URL
> > https://git.qemu.org/git/libslirp.git renders a gitweb page that looks
> > right but has broken links.  The correct gitweb URL listed on
> > https://git.qemu.org/ is https://git.qemu.org/?p=libslirp.git;a=summary,
> > but there's a chance that people will open the HTTPS clone URL in their
> > browser and expect to see gitweb working.
> > 
> > Is it possible to tweak the Apache configuration so that
> > https://git.qemu.org/git/libslirp.git[/] redirects to the working gitweb
> > URL?
> > 
> > The tricky part is not breaking HTTPS git clone, which accesses URLs
> > below https://git.qemu.org/git/libslirp.git/ :).
> 
> I know that's not quite the answer to your question, but if you look
> for example at
> 
>   https://git.zx2c4.com/cgit
> 
> you'll see that the same URL can be used both for viewing with a
> browser *and* cloning.
> 
> Basically with cgit all requests go through the CGI script, and an
> advantage of that is that you don't even need to call
> 
>   git update-server-info
> 
> to make the repository accessible via HTTPs. It's also pretty fast
> and extremely easy to setup. Maybe consider switching from gitweb
> to it?

Thanks, switching to cgit is an option.  Let's see what Jeff thinks.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-09-02  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 15:48 [Qemu-devel] git.qemu.org gitweb misrenders on git/ URLs Stefan Hajnoczi
2019-08-29 16:13 ` Andrea Bolognani
2019-09-02  9:25   ` Stefan Hajnoczi [this message]
2019-09-02 10:35     ` Jeff Cody
2019-09-05  8:20       ` Stefan Hajnoczi

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=20190902092509.GC9069@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=abologna@redhat.com \
    --cc=jeff@codyprime.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).