git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Lea Wiemann <lewiemann@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] gitweb: Extend project_index file format by project description
Date: Sat, 21 Jun 2008 18:09:07 +0200	[thread overview]
Message-ID: <200806211809.07763.jnareb@gmail.com> (raw)
In-Reply-To: <485D1E76.6090709@gmail.com>

Lea Wiemann wrote:
> Jakub Narebski wrote:
>> 
>> The goal is to first, improve performance; and second, to be possible
>> to have single place for all info (well, amost all info) needed to
>> generate projects list.
> 
> I'm not sure if I understand your objective correctly.  If this is 
> exclusively about performance, may I suggest you wait with this till I 
> have implemented caching?  Regenerating the project list might end up 
> being fast enough that it won't matter at all; so no reason to 
> complicate the code.
> 
> If it's about the convenience of maintaining project descriptions in a 
> central place, sure, that's fine.

It is about both, but I think mainly about convenience of maintaining 
(having) all static data about project in one place (well, almost all: 
there is README.html, but it is not visible in projects list page).

What we gain in performance generating projects list (when caching is 
disabled for some reason, like limited quota or/and not installed 
memcached), we might lose when generating project pages (with project 
description).

-- 
Jakub Narebski
Poland

      reply	other threads:[~2008-06-21 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-21 13:40 [RFC/PATCH] gitweb: Extend project_index file format by project description Jakub Narebski
2008-06-21 15:29 ` Lea Wiemann
2008-06-21 16:09   ` Jakub Narebski [this message]

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=200806211809.07763.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lewiemann@gmail.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).