git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Use config file or file for repository owner's name.
Date: Thu, 31 Jan 2008 01:02:50 -0200	[thread overview]
Message-ID: <20080131030250.GA10011@c3sl.ufpr.br> (raw)
In-Reply-To: <7vsl0eg16c.fsf@gitster.siamese.dyndns.org>

On Wed, Jan 30, 2008 at 06:48:43PM -0800, Junio C Hamano wrote:
> Bruno Cesar Ribas <ribas@c3sl.ufpr.br> writes:
> 
> > On Tue, Jan 29, 2008 at 10:16:16PM -0800, Junio C Hamano wrote:
> >> Bruno Ribas <ribas@c3sl.ufpr.br> writes:
> >> 
> >> <snip> 
> >> I am not sure about the effect of this change on a large scale
> >> site.  If you do not have the project list file, originally we
> >> just needed a stat per project, but now you open an extra file
> >> (either "owner" or "config") and read it, once per every
> >> project.
> >
> > Opening the extra file has same problem as the description file. And, as
> > gitweb allow us to create  "description" and "cloneurl" file there is no 
> > problem having another file to open instead finding out who is the owner of
> > the directory asking to the filesystem.
> 
> We heard the same argument when cloneurl was added, and a
> newcomer who does not know that may rightly use the same
Well, it worked for cloneurl.

> argument.  But I think we should work towards _reducing_ the
> number of such ad-hoc one-line-per-information files, not using
> existing ones as an excuse to add _more_ of them.

Okay, I agree with you. We need to centralize information.
One idea use $GIT_DIR/config only, sharing any other information. But I
don't like the idea do parse $GIT_DIR/config everytime. Unless it caches
gitweb only information in one line.

Another Idea is to use $GIT_DIR/gitweb.conf with information [like the
cached above], but generated by the gitweb admin.

Other to continue with all those files, but creating a gitweb.d/* .

That's what I can think 1:02am =(

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

  reply	other threads:[~2008-01-31  3:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  5:28 [PATCH] gitweb: Use config file or file for repository owner's name Bruno Ribas
2008-01-30  5:28 ` [PATCH] gitweb: Update gitweb/README to include the new per-repository configuration Bruno Ribas
2008-01-30  6:16 ` [PATCH] gitweb: Use config file or file for repository owner's name Junio C Hamano
2008-01-31  2:36   ` Bruno Cesar Ribas
2008-01-31  2:48     ` Junio C Hamano
2008-01-31  3:02       ` Bruno Cesar Ribas [this message]
2008-01-31  3:06       ` Junio C Hamano
2008-01-31  3:36         ` Jakub Narebski
2008-01-31 11:12           ` Johannes Schindelin
2008-02-01  0:17             ` Jakub Narebski
2008-02-04 13:35               ` Bruno Cesar Ribas
2008-02-04 14:00                 ` Jakub Narebski
2008-02-05  4:41         ` Bruno Cesar Ribas
2008-02-05 10:04           ` Jakub Narebski
2008-02-05 14:28             ` Bruno Cesar Ribas
2008-02-07  4:12           ` Bruno Cesar Ribas

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=20080131030250.GA10011@c3sl.ufpr.br \
    --to=ribas@c3sl.ufpr.br \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).