From: "Lars Hjemli" <hjemli@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Johan Herland" <johan@herland.net>,
git@vger.kernel.org, "Jakub Narebski" <jnareb@gmail.com>,
"Kristian Høgsberg" <hoegsberg@gmail.com>
Subject: Re: CGit and repository list
Date: Tue, 16 Sep 2008 00:04:01 +0200 [thread overview]
Message-ID: <8c5c35580809151504r24e1b067ye0a085ad9e128bfb@mail.gmail.com> (raw)
In-Reply-To: <20080913194938.GI10360@machine.or.cz>
On Sat, Sep 13, 2008 at 9:49 PM, Petr Baudis <pasky@suse.cz> wrote:
> On Sat, Sep 13, 2008 at 01:20:50AM +0200, Lars Hjemli wrote:
>> I guess I could add support for something like
>>
>> scan-paths=/pub/git
>>
>> in cgitrc (and optionally store the result of the scan as another
>> cgitrc-file in the cache directory). Would that improve things for
>> you?
>
> Yes, certainly.
Ok, for now I've added a --scan-tree=<path> commandline option which
will make cgit print a sorted list of the repositories found to
stdout. If/when this does a reasonable job on repo.or.cz I can look
into some form of automatic rescanning (enabled from cgitrc).
>> > Unfortunately, the recommended RewriteRule is not working - it does not
>> > play well together with query parameters cgit is using, so e.g. browsing
>> > past commits does not work.
I've also pushed support for PATH_INFO. This allows you to drop the
rewriterules from httpd.conf and the 'virtual-url' option from cgitrc
and still get the 'nice' urls.
> I wonder why
>
> http://repo.or.cz/c/libc.git/
>
> has such a funny-looking summary page.
It's due to cgits terrible functions for parsing commits and tags.
I've pushed a reworked patch which should make the parsing more robust
and thus also render glibc.git correctly.
Finally, and probably more interesting for freedesktop.org than
repo.or.cz, is the support for repolist filtering by url prefix
(compare http://hjemli.net/git and http://hjemli.net/git/xorg for a
minimal example).
This is all available from the master branch in
git://hjemli.net/pub/git/cgit, enjoy!
--
larsh
next prev parent reply other threads:[~2008-09-15 22:05 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 ` Lars Hjemli [this message]
2008-09-14 17:14 ` CGit and repository list 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
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=8c5c35580809151504r24e1b067ye0a085ad9e128bfb@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=hoegsberg@gmail.com \
--cc=jnareb@gmail.com \
--cc=johan@herland.net \
--cc=pasky@suse.cz \
/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).