git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Fitzsimons <robfitz@273k.net>
To: Junio C Hamano <junkio@cox.net>
Cc: Robert Fitzsimons <robfitz@273k.net>,
	Jakub Narebski <jnareb@gmail.com>,
	Martin Langhoff <martin.langhoff@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] gitweb: New feature last_modified_ref.
Date: Sat, 30 Dec 2006 00:12:18 +0000	[thread overview]
Message-ID: <20061230001218.GH6558@localhost> (raw)
In-Reply-To: <7vlkkqms8n.fsf@assigned-by-dhcp.cox.net>

> I somehow suspect this is solving the problem with a wrong
> tradeoff.

I think the main problem is that we are trying to fix possible
performance problems with the latest version, just because they might
cause a major problem on kernel.org.

At this point I think we should get the latest version loaded and see
what the real problems are.

Robert

      reply	other threads:[~2006-12-30  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-29 18:58 [PATCH] gitweb: New feature last_modified_ref Robert Fitzsimons
2006-12-29 19:12 ` Junio C Hamano
2006-12-30  0:12   ` Robert Fitzsimons [this message]

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=20061230001218.GH6558@localhost \
    --to=robfitz@273k.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=junkio@cox.net \
    --cc=martin.langhoff@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).