git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Use config file or file for repository owner's name.
Date: Wed, 30 Jan 2008 18:48:43 -0800	[thread overview]
Message-ID: <7vsl0eg16c.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080131023629.GB7778@c3sl.ufpr.br> (Bruno Cesar Ribas's message of "Thu, 31 Jan 2008 00:36:29 -0200")

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
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.

  reply	other threads:[~2008-01-31  2:49 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 [this message]
2008-01-31  3:02       ` Bruno Cesar Ribas
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=7vsl0eg16c.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ribas@c3sl.ufpr.br \
    /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).