git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH] gitweb: Extend project_index file format by project description

From
LWLea Wiemann <lewiemann@gmail.com>
Date
Jun 21, 2008, 15:29 UTC
Message-ID
<485D1E76.6090709@gmail.com>
In-Reply-To
<200806211540.58929.jnareb@gmail.com>
Jakub Narebski wrote:
> This is an RFC mainly because I don't know if it wouldn't conflict
> with Lea Wiemann work on adding caching support to gitweb;

If you're talking about merge conflicts, it applies fine on my current working copy. (There's trailing whitespace on the "@pr_info =" line, by the way.)

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

-- Lea
Previous: Jakub NarebskiNext: Jakub Narebski
Message 2 of 3 in “gitweb: Extend project_index file format by project description”
  1. gitweb: Extend project_index file format by project descriptionJakub Narebski, Jun 21, 2008
  2. Lea WiemannJun 21, 2008
  3. Jakub NarebskiJun 21, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.