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

[PATCH 0/3] gitweb: Improve reading of repo config

From
Jakub Narebski <jnareb@gmail.com>
Date
Nov 2, 2007, 23:41 UTC
Message-ID
<1194046880-29941-1-git-send-email-jnareb@gmail.com>

This series of patches introduces single-call reading of gitweb-related part of repository configuration in gitweb. Instead of calling git-config once for each config variable we check, read all variables at once for first request of repo config variable.

First patch adds test to check if our changes do not break gitweb too badly, second one introduces mentioned above "eager" repo config reading, and third makes use of the fact that adding new configuration variables to check is not that costly now.

Table of contents:
==================
 [PATCH 1/3] gitweb: Add tests for overriding gitweb config with repo config
 [PATCH 2/3] gitweb: Read repo config using 'git config -z -l'
 [PATCH 3/3] gitweb: Use config file for repository description and URLs
Diffstat:
=========
 gitweb/gitweb.perl |   82 +++++++++++++++++++++----------------------------
 1 files changed, 33 insertions(+), 47 deletions(-)
-- 
Jakub Narebski, Poland
git version 1.5.3.5
Next: Jakub Narebski
Message 1 of 4 in “gitweb: Improve reading of repo config”
  1. 0/3 gitweb: Improve reading of repo configJakub Narebski, Nov 2, 2007
  2. 1/3 gitweb: Add tests for overriding gitweb config with repo configJakub Narebski, Nov 2, 2007
  3. 2/3 gitweb: Read repo config using 'git config -z -l'Jakub Narebski, Nov 2, 2007
  4. 3/3 gitweb: Use config file for repository description and URLsJakub Narebski, Nov 2, 2007

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.