From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: .git/info/refs
Date: Wed, 24 Jan 2007 10:28:56 +0100 [thread overview]
Message-ID: <ep78r0$h2u$1@sea.gmane.org> (raw)
In-Reply-To: 45B70D06.3050506@zytor.com
H. Peter Anvin wrote:
> Would it be an incompatible change to add the commit date (and perhaps
> the author date) to .git/info/refs? I believe that would make it
> possible to dramatically (orders of magnitude) speed up the generation
> of the gitweb index page, which is easily the most expensive gitweb page
> to generate.
With new gitweb and new git it is not that expensive. It is now one call
to git-for-each-ref per repository.
Besides, we can't rely that .git/info/refs is up to date, or even exists.
It is for dumb protocols, not for gitweb.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-01-24 9:28 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 ` Jakub Narebski [this message]
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 ` .git/info/refs Jakub Narebski
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='ep78r0$h2u$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.