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

Re: Experimental TDB support for GIT REFS

From
Shawn Pearce <spearce@spearce.org>
Date
Jun 28, 2014, 00:37 UTC
Message-ID
<CAJo=hJu3QD09JccSvUrpnNSpFE5ppDHEzozkKyZZAyutvCQTGg@mail.gmail.com>
In-Reply-To
<CAL=YDWn-CGZGr5bXNTiZmzr4-w_8CERx3r2bmLWbczqJ0Sn7dg@mail.gmail.com>
On Fri, Jun 27, 2014 at 2:30 PM, Ronnie Sahlberg <sahlberg@google.com> wrote:
Show 17 quoted lines
> List,
>
> One of my ref transaction aims is to make define a stable public API
> for accessing refs.
> Once this is done I want to make it possible to replace the current
> .git/refs/* model with a
> different type of backend.
> In my case I want to add support to store all refs and reflogs in a TDB database
> but once we have a pluggable backend framework for refs, if someone
> wants to store the refs
> in a SQL database, that should be fairly trivial too.
>
> There are a few series queued before this becomes possible, but is
> anyone wants to test or play with my "git can use TDB database" you
> can find an implementation of this at
>
> https://github.com/rsahlberg/git/tree/backend-struct-tdb
Interesting! But the link 404s :(
Previous: Ronnie SahlbergNext: Ronnie Sahlberg
Message 2 of 4 in “Experimental TDB support for GIT REFS”
  1. Ronnie SahlbergJun 27, 2014
  2. Shawn PearceJun 28, 2014
  3. Ronnie SahlbergJul 2, 2014
  4. Ronnie SahlbergJul 2, 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.