public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Nagy Balázs" <js@iksz•hu>
To: Jakub Narebski <jnareb@gmail•com>
Cc: Bruno Cesar Ribas <ribas@c3sl•ufpr.br>, git@vger•kernel.org
Subject: Re: [PATCH] Added sub get_owner_file which checks if there's a file with project owner name
Date: Tue, 29 Jan 2008 21:53:46 +0100	[thread overview]
Message-ID: <479F925A.5020401@iksz.hu> (raw)
In-Reply-To: <200801291628.21026.jnareb@gmail.com>

Hi,

Jakub Narebski wrote:
> But I think if IO matters it is better to generate projects list; you
> can even use gitweb for that, or you can simply add a line with URL
> escaped project name (project path) relative to $projectroot, separated
> by space from the URL escaped (URI-encoded) project owner.  See also
> "Gitweb repositories" section in gitweb/INSTALL.  Adding projects is
> rare event.
>   
Are you talking about I/O of an all-in CGI script?  We can tune the 
performance of this script, but changing the GIT_DIR structure just 
because of a simple script is a bit overkill to me.

What if this script creates the $projects_list file, for example when 
the $projectroot's mtime changes?  We can even hold mtime info for every 
project's config file.

Regards:
-- 
Balazs Nagy

  parent reply	other threads:[~2008-01-29 21:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29  3:36 [PATCH] Added sub get_owner_file which checks if there's a file with project owner name Bruno Ribas
2008-01-29 11:26 ` Jakub Narebski
2008-01-29 14:25   ` Bruno Cesar Ribas
2008-01-29 15:28     ` Jakub Narebski
2008-01-29 17:22       ` Bruno Cesar Ribas
2008-01-29 18:27         ` Jakub Narebski
2008-01-29 20:53       ` Nagy Balázs [this message]
2008-01-29 21:36         ` Jakub Narebski
2008-01-30 15:59           ` Nagy Balázs
2008-02-01 13:18             ` Jakub Narebski
2008-02-01 16:11               ` Nagy Balázs
2008-02-01 19:10                 ` Robin Rosenberg

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=479F925A.5020401@iksz.hu \
    --to=js@iksz$(echo .)hu \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jnareb@gmail$(echo .)com \
    --cc=ribas@c3sl$(echo .)ufpr.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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