From: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
Date: Fri, 08 Feb 2008 13:51:50 GMT
Subject: Re: Adding gitweb.owner, last shot
Message-ID: <20080208135150.GB30264@c3sl.ufpr.br>
In-Reply-To: <m3abmb4tyx.fsf@localhost.localdomain>

On Fri, Feb 08, 2008 at 02:34:55AM -0800, Jakub Narebski wrote:
> Bruno Ribas <ribas@c3sl.ufpr.br> writes:
> 
><snip> 
> Pasky, could you please try to benchmark this (well, at least without
> gitweb.owner set) on a _real_ large set of repositories?

And I'd like to know what this machine runs! If it is git dedicated, or
shares with something else.

If it is git dedicated, it makes time better as disk IO will not be severe.

>  
> > The idea of creating only the gitweb.owner can be a case of study to
> > centralize all gitweb repository configuration in one file. Maybe even
> > change the way $projects_list is formated, as gitweb.cgi needs to check
> > repository configuration to get repository description to generate
> > project_list page, we could just list repository's directories.
> 
> I was thinking about git-config-like format (but simplified to make it
> easy to parse it in Perl, just like git-cvsserver configuration), in
> the form of
> 
> [gitweb "<repository path, relative to $projectroot>"]
>         description = <project description>
>         url = <first URL>
>         url = <seconf URL>
>         owner = <repository owner>
> 
> The problem with parsing lies (among others) in the in-line comments,
> novalue keys, and key after section, I think...
> 
> -- 
> Jakub Narebski
> Poland
> ShadeHawk on #git

-- 
Bruno Ribas - ribas@c3sl.ufpr.br
http://web.inf.ufpr.br/ribas
C3SL: http://www.c3sl.ufpr.br