All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.H." <warthog9@eaglescrag.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
	git@vger.kernel.org,
	"John 'Warthog9' Hawley" <warthog9@kernel.org>,
	Petr Baudis <pasky@ucw.cz>,
	admin@repo.or.cz
Subject: Re: [RFC] Implementing gitweb output caching - issues to solve
Date: Wed, 08 Dec 2010 21:28:13 -0800	[thread overview]
Message-ID: <4D0068ED.8070409@eaglescrag.net> (raw)
In-Reply-To: <7v62v3ikqj.fsf@alter.siamese.dyndns.org>

On 12/08/2010 09:22 PM, Junio C Hamano wrote:
> "J.H." <warthog9@eaglescrag.net> writes:
> 
>> P.S. Most of this e-mail was written a couple of weeks ago, I found it
>> in my drafts folder and wanted to get it out along with a note that I've
>> got v8 percolating. -JH
> 
> Thanks.  Is "Tomorrow morning" relative to "a couple of weeks ago"? ;-)

No tomorrow morning is relative to today - so ~12hrs from now, ish,
maybe big ISH ;-)

I finished up the patch series today.  The series itself is already
pushed out to my repo on kernel.org

http://git.kernel.org/?p=git/warthog9/gitweb.git;a=shortlog;h=refs/heads/gitweb-ml-v8

just wanted to let that stew a bit before pushing it out to the mailing
list, since it is now an 18 part patch :-/

- John 'Warthog9' Hawley

  reply	other threads:[~2010-12-09  5:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 16:21 [RFC] Implementing gitweb output caching - issues to solve Jakub Narebski
2010-12-09  1:31 ` J.H.
2010-12-09  5:22   ` Junio C Hamano
2010-12-09  5:28     ` J.H. [this message]
2010-12-09 22:30   ` Jakub Narebski
2010-12-09 22:52     ` Jonathan Nieder
2010-12-10  3:17       ` Olaf Alders
2010-12-10  4:11         ` Jonathan Nieder
2010-12-10  4:46         ` J.H.

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=4D0068ED.8070409@eaglescrag.net \
    --to=warthog9@eaglescrag.net \
    --cc=admin@repo.or.cz \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=pasky@ucw.cz \
    --cc=warthog9@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.