On Fri, Feb 10, 2012 at 4:39 PM, Christian Couder <christian.couder@xxxxxxxxx> wrote: > Hi, > > On Fri, Feb 10, 2012 at 8:12 AM, Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx> wrote: >> >> All these involve unpack_trees(), which is full tree operation. The >> bigger your worktree is, the slower it is. Another good reason to >> split unrelated parts into separate repositories. > > Maybe having different "views" would be enough to make a smaller > worktree and history, so that things are much faster for a developper? > > (I already suggested "views" based on "git replace" in this thread: > http://thread.gmane.org/gmane.comp.version-control.git/177146/focus=177639) That's more or less what I did with the subtree clone series [1] and ended up doing narrow clone [2]. The only difference between the two are how to handle partial worktree/index. The former uses git-replace to seal any holes, the latter tackles at pathspec level and is generally more elegant. The worktree part from that work should be usable in full clone too. I am reviving the series and going to repost it soon. Have a look [3] if you are interested. [1] http://thread.gmane.org/gmane.comp.version-control.git/152347 [2] http://thread.gmane.org/gmane.comp.version-control.git/155427 [3] https://github.com/pclouds/git/commits/narrow-clone -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html