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

RFC: working with sparse work-copy: where to start?

From
MTMichael S. Tsirkin <mst@mellanox.co.il>
Date
Dec 31, 2006, 10:42 UTC
Message-ID
<20061231104217.GE26552@mellanox.co.il>

Hi! I've been thinking about working in a sparsely-populated work copy. E.g. svn will let you do a checkout of a specific sub-directory and do all your development there assuming you only care about changes in that directory. Ideally, it would be possible to specify a set of directories that I care about.

git does close to what I want if I do git-clone -n and then git-checkout <subdirectory>.

However,
1. This re-creates the same directory structure that the repository has.
   Especially for when this directory resides deep in the original repo
   tree structure, it would be nice to be able relocate the directory anywhere.
2. The rest of the tree is checked-out whenever I pull from the central repo.
3. git-commit would list all files I didn't check out as removed.

I wonder how hard would it be to add such support? I tried looking at 2 - is builtin-merge-file.c the only place where the checkout is done on merge?

What other commands need to be fixed for this to work?
-- 
MST
Next: Junio C Hamano
Message 1 of 3 in “RFC: working with sparse work-copy: where to start?”
  1. Michael S. TsirkinDec 31, 2006
  2. Junio C HamanoDec 31, 2006
  3. Michael S. TsirkinJan 1, 2007

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.