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

Re: [RFD] Gitweb caching, part 1 (long)

From
Frank Lichtenheld <frank@lichtenheld.de>
Date
Mar 19, 2008, 08:21 UTC
Message-ID
<20080319082158.GY18624@mail-vs.djpig.de>
In-Reply-To
<200803190154.55532.jnareb@gmail.com>
On Wed, Mar 19, 2008 at 01:54:53AM +0100, Jakub Narebski wrote:
Show 7 quoted lines
> Because of that I think it would be possible to represent data to be
> saved (cached) in the ini-like extended git config format.  Then
> gitweb could either (re)use config parser in Perl used by
> git-cvsserver (which accepts subset of valid config format), or 
> "git config --file=<path> -z -l" to slurp data in more parseable
> format... but if we do that, we could choose this format or variation
> of it as our serialization format.
git-cvsserver uses "git config -l", too.
Gruesse,
-- 
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/
Previous: Jakub NarebskiNext: Jakub Narebski
Message 2 of 4 in “[RFD] Gitweb caching, part 1 (long)”
  1. Jakub NarebskiMar 19, 2008
  2. Frank LichtenheldMar 19, 2008
  3. [RFD] Gitweb caching, part 2 (long)Jakub Narebski, Mar 25, 2008
  4. [RFD] Gitweb caching, part 3: examining Perl modules for caching (long)Jakub Narebski, Mar 29, 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.