Re: .gitlink for Summer of Code

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Mar 25, 2007, 15:20 UTC
Message-ID: <vpqvegpe4e1.fsf@olympe.imag.fr>
In-Reply-To: <1174825838.12540.5.camel@localhost>

Eric Lesh <eclesh@ucla.edu> writes:

> .gitlink is for a lightweight checkout of a branch into a separate
> directory on the local filesystem.

I think it's a pitty to restrict yourself to _local_ filesystem. There are tons of cases where you have a fast, non-NFS, access to a machine and would like to host your repository there.

That said, I suppose removing this restriction moves the solution from the category "quick and efficient hack" to something much harder.

> A .gitlink'ed checkout has its own index+HEAD, but otherwise refers
> back to the main repository for objects, refs, etc.

Stupid question: why .gitlink, and not .git/link or so? This file is not versionned, I don't think it should be in the working tree.

-- 
Matthieu

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