Re: Change set based shallow clone

From: Jon Smirl <jonsmirl@gmail.com>
Date: Sep 11, 2006, 02:11 UTC
Message-ID: <9e4733910609101911y25005ca6v7dfdbf20f95577f2@mail.gmail.com>
In-Reply-To: <7vfyezqlny.fsf@assigned-by-dhcp.cox.net>

On 9/10/06, Junio C Hamano <junkio@cox.net> wrote:

> I do not see any advantage of making such a phoney object at
> all, but I do agree that the current one file per ref can be
> less than optimal when your repository has tons of tags or
> refs.

Here's a hack, instead of of putting the sha inside the file, put the sha into the filename.

master_86a8534ba23a5532f6d0ddd01ecd8f02f662cf78

Now you can just do a directory listing and get all of the data quickly. To keep the existing porcelain working add a symlink.

ln -s master_86a8534ba23a5532f6d0ddd01ecd8f02f662cf78 master

You might want the sha1 encoded names in a new directory

-- 
Jon Smirl
jonsmirl@gmail.com

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