Re: Notes on Using Git with Subprojects
- From
- Michael S. Tsirkin <mst@mellanox.co.il>
- Date
- Sep 28, 2006, 15:02 UTC
- Message-ID
- <20060928150224.GE28790@mellanox.co.il>
- In-Reply-To
- <7vhcyt81gn.fsf@assigned-by-dhcp.cox.net>
Quoting r. Junio C Hamano <junkio@cox.net>:
Show 6 quoted lines
> Avoiding checking out parts of the project tree that you do not > care about while you work on such a single large project is > another interesting and useful area to think about, but I would > say at that point it is not about subproject at all -- it is > about working in a sparsely populated working tree of a single > project.
I agree completely - at least as far as I'm concerned, working in a sparsely populated working tree is what it's all about. For example, sometimes I am just editing documentation and it would be nice
It's easy to check out just a subdirectory the first time:
>git checkout master `git-ls-tree -r --name-only master subdirectory` >echo ref: refs/heads/master > .git/HEAD
but when you try a pull/rebase git will check out all of the tree.
Is there some way to avoid this?
-- MST