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

Re: [RFC PATCH 0/7] Implement ref namespaces as a ref storage backend

From
Stefan Beller <sbeller@google.com>
Date
Aug 14, 2017, 17:00 UTC
Message-ID
<CAGZ79kZz16kwwMOxoi+6UksT2CaPBU5O+r3QzxfrUBf8c3whhg@mail.gmail.com>
In-Reply-To
<20170813193611.4233-1-richard.maw@gmail.com>
Show 5 quoted lines
> Technical description
> =====================
>
> This patch series adds a new refs backend, stacking on top of the files backend,
> based on whether `core.namespace` is set in git config.

Currently there is another Big Thing getting started in in the refs backend. https://public-inbox.org/git/CAJo=hJtg0PAVHT1phbArdra8+4LfnEEuaj3fBid==BXkZghi8g@mail.gmail.com/ Maybe it is worth looking into that as well? Reftables solve the problem of scaling (i.e. a repo containing a million refs works just fine, and fast(!) for reading/writing refs, which is not the case for packed refs)

Previous: Richard MawNext: Junio C Hamano
Message 9 of 13 in “Implement ref namespaces as a ref storage backend”
  1. 0/7 Implement ref namespaces as a ref storage backendRichard Maw, Aug 13, 2017
  2. 1/7 Expose expand_namespace APIRichard Maw, Aug 13, 2017
  3. 2/7 Add git_configset_add_standardRichard Maw, Aug 13, 2017
  4. 3/7 Add helper for skipping namespace prefixesRichard Maw, Aug 13, 2017
  5. 4/7 Autocreate reflogs for namespaced refsRichard Maw, Aug 13, 2017
  6. 5/7 Treat namespaced HEAD and refs/bisect as per-worktreeRichard Maw, Aug 13, 2017
  7. 6/7 Add namespaced ref backendRichard Maw, Aug 13, 2017
  8. 7/7 Plumb in namespaced ref storeRichard Maw, Aug 13, 2017
  9. Stefan BellerAug 14, 2017
  10. Junio C HamanoAug 15, 2017
  11. Richard MawAug 24, 2017
  12. Michael HaggertyAug 24, 2017
  13. Richard MawAug 30, 2017

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.