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

Re: Pluggable backends for refs,wip

From
NWNico Williams <nico@cryptonector.com>
Date
Aug 5, 2014, 21:56 UTC
Message-ID
<CAK3OfOiu39H8oZMKjra97ZNLHNatNYtFwr8Do_QwoxGXzg4SGw@mail.gmail.com>
In-Reply-To
<CAL=YDWk5C+bQS76_+jx1BSYSxecCxaS95RG181ecbJBLCNWLkQ@mail.gmail.com>

Personally (a user of, not a maintainer of, git) I really want some alternative backends. In particular I'm after something like Fossil's use of SQLite3; I want a SQLite3 backend for several reasons, not the least of which is the power of SQL for looking at history.

I'm not sure that I necessarily want a daemon/background process. I get the appeal (add inotify and bingo, very fast git status, always), but it seems likely to add obnoxious failure modes.

As to a SQLite3-type backend, I am of two minds: either add it as a bolt-on to the builtin backend, or add it as a first-class backend that replaces the builtin one. The former is nice because the SQLite3 DB becomes more of a cache/index and query engine than a store, and can be used without migrating any repos, but the latter is also nice because SQLite3 provides strong ACID transactional semantics on local filesystems.

Nico --

Previous: Ronnie SahlbergNext: Ronnie Sahlberg
Message 2 of 6 in “Pluggable backends for refs,wip”
  1. Ronnie SahlbergAug 5, 2014
  2. Nico WilliamsAug 5, 2014
  3. Ronnie SahlbergAug 5, 2014
  4. Nico WilliamsAug 5, 2014
  5. Michael HaggertyAug 7, 2014
  6. Ronnie SahlbergAug 8, 2014

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.