git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lars Hjemli" <hjemli@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
	"Petr Baudis" <pasky@suse.cz>,
	git@vger.kernel.org
Subject: Re: CGit and repository list
Date: Fri, 12 Sep 2008 18:12:43 +0200	[thread overview]
Message-ID: <8c5c35580809120912r22f16063sa779cd2ce43dd131@mail.gmail.com> (raw)
In-Reply-To: <20080912160006.GI22960@spearce.org>

On Fri, Sep 12, 2008 at 6:00 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Jakub Narebski <jnareb@gmail.com> wrote:
>> Petr Baudis wrote:
>> >
>> >   this finally tripped me over and I wanted to quickly add cgit as an
>> > alternate viewing interface at repo.or.cz. [...]
>>
>> Or you can wait a little while for "smart" HTTP server, which I guess
>> also generates automatically or/and on the fly objects/info/packs and
>> info/refs required by "dumb" protocols clients (including old HTTP
>> clients).
>
> The automatic generation of objects/info/packs and info/refs is
> planned for support in the smart CGI, but it doesn't help the
> "gitweb URL is same as clone URL" concept.  For that you need your
> HTTP server to know how to issue some requests to gitweb and others
> to the smart CGI or to the filesystem.

In the case of cgit this should work transparently.

>
>> P.S. Could you please gather some statistics to compare the period
>> before and after installing "smart" HTTP server (and after smart
>> clients became widespread).
>
> Well, it would help if there was a working implementation of the
> "smart" HTTP server.  ;-)

I'll try to come up with a prototype for the smart server as part of cgit ;-)

--
larsh

  reply	other threads:[~2008-09-12 16:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  4:47 configuring git public repository sagi4
2008-09-12 12:33 ` Ciprian Dorin Craciun
2008-09-12 12:57   ` Jakub Narebski
2008-09-12 14:36     ` Lars Hjemli
2008-09-12 14:58       ` CGit and repository list Petr Baudis
2008-09-12 15:10         ` Lars Hjemli
     [not found]           ` <200809121812.40920.johan@herland.net>
2008-09-12 22:48             ` Petr Baudis
2008-09-12 23:20               ` Lars Hjemli
2008-09-13 19:49                 ` Petr Baudis
2008-09-13 20:02                   ` Lars Hjemli
2008-09-14  7:53                     ` [CGIT PATCH] parsing.c: handle unexpected commit/tag content Lars Hjemli
2008-09-14  8:52                       ` Lars Hjemli
2008-09-15 22:04                   ` CGit and repository list Lars Hjemli
2008-09-14 17:14               ` Kristian Høgsberg
2008-09-14 17:22                 ` Kristian Høgsberg
2008-09-14 18:01                   ` Lars Hjemli
2008-09-12 15:54         ` Jakub Narebski
2008-09-12 16:00           ` Shawn O. Pearce
2008-09-12 16:12             ` Lars Hjemli [this message]
2008-09-12 16:05           ` Petr Baudis
2008-09-12 16:08             ` Shawn O. Pearce
2008-09-12 16:20               ` Petr Baudis
2008-09-12 16:22                 ` Shawn O. Pearce
2008-09-12 17:40             ` Jakub Narebski
2008-09-12 17:45               ` Shawn O. Pearce
2008-09-12 19:13               ` Petr Baudis

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=8c5c35580809120912r22f16063sa779cd2ce43dd131@mail.gmail.com \
    --to=hjemli@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=pasky@suse.cz \
    --cc=spearce@spearce.org \
    /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).