From: Kris Shannon <kris@shannon.id.au>
To: "J.H." <warthog9@kernel.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [Gitweb-caching][RFC] Major updates - kernel.org updated
Date: Thu, 8 Oct 2009 19:26:40 +1100 [thread overview]
Message-ID: <e51f4f550910080126s5885e5d6jc91e3b3ec0f4fe3e@mail.gmail.com> (raw)
In-Reply-To: <4ACD6FED.4080308@kernel.org>
2009/10/8 J.H. <warthog9@kernel.org>:
> So I'm going to re-open the can of worms over caching again, and see what it
> would take to get this merged into mainline. Obviously a patch clean-up (my
> tree is a lot more organic than mainline) is needed, but I thought I'd try
> and get an idea of where I need to start steering all of this.
>
> - John 'Warthog9' Hawley
For everyone playing at home, I found J.H.'s tree at:
git://git.kernel.org/pub/scm/git/warthog9/gitweb.git
or Gitweb interface :)
http://git.kernel.org/?p=git/warthog9/gitweb.git
- Kris
prev parent reply other threads:[~2009-10-08 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 4:51 [Gitweb-caching][RFC] Major updates - kernel.org updated J.H.
2009-10-08 8:26 ` Kris Shannon [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=e51f4f550910080126s5885e5d6jc91e3b3ec0f4fe3e@mail.gmail.com \
--to=kris@shannon.id.au \
--cc=git@vger.kernel.org \
--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 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).