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

Re: [(not so) random thoughts] using git as its own caching tool

From
Mike Hommey <mh@glandium.org>
Date
Dec 12, 2007, 15:48 UTC
Message-ID
<20071212154848.GA19294@glandium.org>
In-Reply-To
<475FFFB7.4010102@op5.se>
On Wed, Dec 12, 2007 at 04:35:19PM +0100, Andreas Ericsson <ae@op5.se> wrote:
Show 12 quoted lines
> A bit of both ;-)
> 
> I like the idea to use the git object store, because that certainly
> has an API that can't be done away with by user config. The reflog
> and its expiration mechanism is subject to human control though, and
> everyone doesn't even have them enabled. I don't for some repos where
> I know I'll create a thousand-and-one loose objects by rebasing,
> --amend'ing and otherwise fiddling with history rewrites.
> 
> Having a tool that works on some repos but not on others because it
> relies on me living with an auto-gc after pretty much every operation
> would be very tiresome indeed.
There is already a tool that relies on reflogs: stash.
Mike
Previous: Andreas EricssonNext: Andreas Ericsson
Message 4 of 6 in “[(not so) random thoughts] using git as its own caching tool”
  1. Pierre HabouzitDec 12, 2007
  2. Mike HommeyDec 12, 2007
  3. Andreas EricssonDec 12, 2007
  4. Mike HommeyDec 12, 2007
  5. Andreas EricssonDec 12, 2007
  6. Pierre HabouzitDec 12, 2007

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.