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

Re: What's cooking in git.git (Nov 2010, #02; Wed, 17)

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 24, 2010, 17:13 UTC
Message-ID
<7vpqtutzkp.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4CEC6E2A.9080605@kernel.org>
"J.H." <warthog9@kernel.org> writes:
> While I don't disagree, being able to support other caching systems
> would be nice, we have this now, it's tested and it works.  I'd argue
> this is a step 1, step 2 case at this point.

I would have to agree; getting some cache layer that is known to work (you are battle testing your updates on a busy site of yours as you develop, right?) early, quick and dirty with minimum changes, is more beneficial than waiting for a large rewrite thats "gets it perfect this time".

> I'm currently working from on top of Jakub's last tree, though I've got
> some questions about his reasoning on a few things now that I've been
> digging into it.
Thanks both for keeping the ball rolling.
Previous: J.H.Next: Jakub Narebski
Message 7 of 9 in “What's cooking in git.git (Nov 2010, #02; Wed, 17)”
  1. Junio C HamanoNov 18, 2010
  2. Jakub NarebskiNov 18, 2010
  3. Junio C HamanoNov 18, 2010
  4. J.H.Nov 18, 2010
  5. Jakub NarebskiNov 20, 2010
  6. J.H.Nov 24, 2010
  7. Junio C HamanoNov 24, 2010
  8. Jakub NarebskiNov 24, 2010
  9. Jakub NarebskiNov 24, 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.