Am 22.04.2012 06:41, schrieb Junio C Hamano: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> As you analyzed correctly, core.worktree lets a GIT_DIR to declare that >> there is a single working tree associated with it. It fundamentally is >> incompatible with new-workdir, which is a hack to let more than one >> working tree associated with a single GIT_DIR. >> >> I however do not think a simplistic "unset core.worktree" is a good >> suggestion, though, as we do not know why the original repository has >> that variable set pointing at somewhere. Blindly removing it will break >> the use of the original repository. If somebody _really_ wants to use >> new-workdir for whatever reason in such a setting, I would imagine that >> doing something like this: >> ... >> may work. > > I am too lazy to try it out myself, but a hack something along the line > of the attached patch _might_ turn out to work well. A quick test worked just fine. Looks like you fixed git-new-workdir to be usable with the new gitfile submodules ;-) -- 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