Re: .git/info/refs

From: Jakub Narebski <jnareb@gmail.com>
Date: Jan 24, 2007, 20:40 UTC
Message-ID: <200701242140.07459.jnareb@gmail.com>
In-Reply-To: <45B7818F.6020805@zytor.com>

H. Peter Anvin wrote:

> Jakub Narebski wrote:

Show 6 quoted lines

>> Besides, we can't rely that .git/info/refs is up to date, or even exists.
>> It is for dumb protocols, not for gitweb.
> 
> Well, SOMETHING needs to be done for this page, since it can take 15 
> minutes or more to generate.  Caching doesn't help one iota, since it's 
> stale before being generated.

The simple and fast solution would be to make post-update hook contain the git-for-each-ref with parameters like in git_get_last_activity, saving e.g. to .git/info/last-committer, and in gitweb read this file if it exist, run git-for-each-ref otherwise (similar to what we used to do with .git/info/refs and git-peek-remote in gitweb).

-- 
Jakub Narebski
Poland