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

Re: Storing Large Flat Namespaces

From
JSJaap Suter <git@jaapsuter.com>
Date
Sep 8, 2008, 04:26 UTC
Message-ID
<loom.20080908T042124-621@post.gmane.org>
In-Reply-To
<21d738060809071858p703149ccmbec0276ad4ad8f88@mail.gmail.com>
> I'm investigating the possibility of using Git to store a large flat
> namespace. As an example, imagine a single directory containing
> thousands or millions of files, each named using a 16-byte guid,
> evenly distributed.

I realize that an obvious suggestion may be to figure out if there is a way to leverage the internal structure of the files to create a more Git-friendly tree layout.

Unfortunately the internal structure is largely opaque to me, and highly dynamic.

Thanks,
Jaap
Previous: Jaap SuterNext: Nicolas Pitre
Message 2 of 3 in “Storing Large Flat Namespaces”
  1. Jaap SuterSep 8, 2008
  2. Jaap SuterSep 8, 2008
  3. Nicolas PitreSep 8, 2008

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.