Re: [PATCH v3 03/14] commit-graph: create git-commit-graph builtin

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 8, 2018, 21:27 UTC
Message-ID: <xmqqzi4jp3y5.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <1518122258-157281-4-git-send-email-dstolee@microsoft.com>

Derrick Stolee <stolee@gmail.com> writes:

> Teach git the 'commit-graph' builtin that will be used for writing and
> reading packed graph files. The current implementation is mostly
> empty, except for a '--pack-dir' option.

Why do we want to use "pack" dir, when this is specifically designed not tied to packfile? .git/objects/pack/ certainly is a possibility in the sense that anywhere inside .git/objects/ would make sense, but using the "pack" dir smells like signalling a wrong message to users.

$ 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.