> H. Peter Anvin wrote: > >>> 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). > Right, this is basically what I'm saying; the question is only whether or not this fits into .git/info/refs or should be a separate file. Either way, I think git-update-server-info should generate all these files. -hpa - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Jan 25 07:45:38 2007
This archive was generated by hypermail 2.1.8 : 2007-01-25 07:50:07 EST