On Wed, Jan 30, 2008 at 06:48:43PM -0800, Junio C Hamano wrote: > Bruno Cesar Ribas <ribas@xxxxxxxxxxxx> writes: > > > On Tue, Jan 29, 2008 at 10:16:16PM -0800, Junio C Hamano wrote: > >> Bruno Ribas <ribas@xxxxxxxxxxxx> 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@xxxxxxxxxxxx http://web.inf.ufpr.br/ribas C3SL: http://www.c3sl.ufpr.br - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
