git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] Implementing gitweb output caching - issues to solve

From
J.H. <warthog9@eaglescrag.net>
Date
Dec 9, 2010, 05:28 UTC
Message-ID
<4D0068ED.8070409@eaglescrag.net>
In-Reply-To
<7v62v3ikqj.fsf@alter.siamese.dyndns.org>
On 12/08/2010 09:22 PM, Junio C Hamano wrote:
Show 7 quoted lines
> "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
Previous: Junio C HamanoNext: Jakub Narebski
Message 4 of 9 in “[RFC] Implementing gitweb output caching - issues to solve”
  1. Jakub NarebskiNov 4, 2010
  2. J.H.Dec 9, 2010
  3. Junio C HamanoDec 9, 2010
  4. J.H.Dec 9, 2010
  5. Jakub NarebskiDec 9, 2010
  6. Jonathan NiederDec 9, 2010
  7. Olaf AldersDec 10, 2010
  8. Jonathan NiederDec 10, 2010
  9. J.H.Dec 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.