Woo hoo, I had this problem, and TortoiseSVN has supported solutions for both add and delete an item from the sparse checkout. http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-checkout.html 1.To add: In windows explorer, Right click on the checked out folder, then use TortoiseSVN ? Repo-Browser to bring up the repository browser. Find the sub-folder you would like to add to …
Jenkins Git Plugin support sparse checkouts since git-plugin 2.1.0 (April, 2014). You will need git >= 1.7.0 for this feature. It is under “Additional Behaviors” -> “Sparse Checkout paths.” See: Jira issue JENKINS-21809
You still need to clone the whole repository, which will have all the files. You could use the –depth flag to only retrieve a limited amount of history. Once the repository is cloned, the read-tree trick limits your “view” of the repository to only those files or directories that are in the .git/info/sparse-checkout file. I …
After I opened an issue on the git-for-windows bug tracker (https://github.com/git-for-windows/git/issues/2803), I found that my issue had already been filed as https://github.com/git-for-windows/git/issues/2777. That issue suggested that I need to set another git flag: git config core.protectNTFS false This (#2777) indeed contains a bypass for the my problem. I hope the git or git-for-windows (who were …
Indeed, thanks to the comments to my post here, it looks like sparse directories are the way to go. I believe the following should do it: svn checkout –depth empty http://svnserver/trunk/proj svn update –set-depth infinity proj/foo svn update –set-depth infinity proj/bar svn update –set-depth infinity proj/baz Alternatively, –depth immediates instead of empty checks out files …
Sparse checkouts are now in Git 1.7. Also see the question “Is it possible to do a sparse checkout without checking out the whole repository first?”. Note that sparse checkouts still require you to download the whole repository, even though some of the files Git downloads won’t end up in your working tree.
Please note that this answer does download a complete copy of the data from a repository. The git remote add -f command will clone the whole repository. From the man page of git-remote: With -f option, git fetch <name> is run immediately after the remote information is set up. Try this: mkdir myrepo cd myrepo …
With Git 2.23 (August 2019), you have the new command git restore (also presented here) git restore –source=HEAD –staged –worktree — aDirectory # or, shorter git restore -s@ -SW — aDirectory That would replace both the index and working tree with HEAD content, like an reset –hard would, but for a specific path. Original answer …
In git version 1.7.9.5 this seems to work to export a single file from a remote git archive –remote=ssh://host/pathto/repo.git HEAD README.md | tar xO This will cat the contents of the file README.md.
Originally, I mentioned in 2012 git archive (see Jared Forsyth’s answer and Robert Knight’s answer), since git1.7.9.5 (March 2012), Paul Brannan’s answer: git archive –format=tar –remote=origin HEAD:path/to/directory — filename | tar -O -xf – But: in 2013, that was no longer possible for remote https://github.com URLs. See the old page “Can I archive a repository?“ …