From: Robert Fitzsimons <robfitz@273k.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Possible optimization for gitweb
Date: Wed, 20 Dec 2006 00:52:04 +0000 [thread overview]
Message-ID: <20061220005204.GC17864@localhost> (raw)
In-Reply-To: <em9mcs$moo$1@sea.gmane.org>
> P.P.S. Do you have any comments to latest "[RFC] gitweb wishlist and TODO
> list" series?
I'll have another read through them tomorrow and see what I come up
with. I've already done a bit of reading up on mod_perl.
Robert
next prev parent reply other threads:[~2006-12-20 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 20:54 [RFC] Possible optimization for gitweb Robert Fitzsimons
2006-12-19 21:45 ` Jakub Narebski
2006-12-20 0:52 ` Robert Fitzsimons [this message]
2006-12-19 22:10 ` Junio C Hamano
2006-12-19 22:22 ` Jakub Narebski
2006-12-20 0:29 ` [PATCH] rev-list: Add a new option --skip Robert Fitzsimons
2006-12-20 1:09 ` Junio C Hamano
2006-12-20 14:59 ` [PATCH] rev-list: Document --skip and add test cases Robert Fitzsimons
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=20061220005204.GC17864@localhost \
--to=robfitz@273k.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).