From: Jakub Narebski <jnareb@gmail•com>
To: "H. Peter Anvin" <hpa@zytor•com>
Cc: git@vger•kernel.org
Subject: Re: .git/info/refs
Date: Wed, 24 Jan 2007 21:40:06 +0100 [thread overview]
Message-ID: <200701242140.07459.jnareb@gmail.com> (raw)
In-Reply-To: <45B7818F.6020805@zytor.com>
H. Peter Anvin wrote:
> Jakub Narebski 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).
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-01-24 20:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 7:38 .git/info/refs H. Peter Anvin
2007-01-24 9:28 ` .git/info/refs Jakub Narebski
2007-01-24 15:55 ` .git/info/refs H. Peter Anvin
2007-01-24 16:02 ` .git/info/refs Johannes Schindelin
2007-01-24 16:24 ` .git/info/refs H. Peter Anvin
2007-01-24 16:38 ` .git/info/refs Johannes Schindelin
2007-01-24 16:41 ` .git/info/refs H. Peter Anvin
2007-01-24 16:52 ` .git/info/refs Johannes Schindelin
2007-01-24 17:06 ` .git/info/refs H. Peter Anvin
2007-01-24 17:25 ` .git/info/refs Jakub Narebski
2007-01-24 17:10 ` .git/info/refs Jakub Narebski
2007-01-24 17:20 ` .git/info/refs Johannes Schindelin
2007-01-25 17:13 ` .git/info/refs H. Peter Anvin
2007-01-26 11:22 ` .git/info/refs Jakub Narebski
2007-01-26 11:41 ` .git/info/refs Junio C Hamano
2007-01-26 16:39 ` .git/info/refs H. Peter Anvin
2007-01-26 17:06 ` .git/info/refs Jakub Narebski
2007-01-26 21:09 ` .git/info/refs Johannes Schindelin
2007-01-26 21:32 ` .git/info/refs H. Peter Anvin
2007-01-26 21:54 ` .git/info/refs H. Peter Anvin
2007-01-24 20:40 ` Jakub Narebski [this message]
2007-01-24 20:44 ` .git/info/refs hpa
2007-01-25 8:14 ` .git/info/refs Johannes Schindelin
2007-01-25 16:12 ` .git/info/refs H. Peter Anvin
2007-01-25 16:50 ` .git/info/refs Johannes Schindelin
2007-01-24 20:45 ` .git/info/refs hpa
2007-01-25 21:28 ` .git/info/refs Junio C Hamano
2007-01-25 21:37 ` .git/info/refs H. Peter Anvin
2007-01-25 21:51 ` .git/info/refs Junio C Hamano
2007-01-25 22:01 ` .git/info/refs H. Peter Anvin
2007-01-25 23:33 ` .git/info/refs Johannes Schindelin
2007-01-27 22:07 ` .git/info/refs H. Peter Anvin
2007-01-31 15:38 ` .git/info/refs Santi Béjar
2007-02-01 14:03 ` .git/info/refs Johannes Schindelin
2007-02-01 16:16 ` .git/info/refs H. Peter Anvin
2007-02-01 16:52 ` .git/info/refs Johannes Schindelin
2007-02-01 16:56 ` .git/info/refs H. Peter Anvin
2007-02-01 17:32 ` .git/info/refs Matthias Lederhofer
2007-02-01 17:51 ` .git/info/refs H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200701242140.07459.jnareb@gmail.com \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=hpa@zytor$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox