worktrees vs. alternates

From: Lars Schneider <larsxschneider@gmail.com>
Date: May 16, 2018, 08:13 UTC
Message-ID: <A33442B1-B37D-42E1-9C58-8AB583A43BC9@gmail.com>

Hi,

I am looking into different options to cache Git repositories on build machines. The two most promising ways seem to be git-worktree [1] and git-alternates [2].

I wonder if you see an advantage of one over the other?

My impression is that git-worktree supersedes git-alternates. Would that be a fair statement? If yes, would it makes sense to deprecate alternates for simplification?

Thanks, Lars

[1] https://git-scm.com/docs/git-worktree [2] https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates

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