Hmmmmm.... This is a good fix to adjust to the new world order introduced by Dscho's rewrite of work-tree stuff, where the rules are: * When GIT_DIR is set and GIT_WORK_TREE is not, GIT_DIR is used to read config file, to figure out core.worktree. When core.worktree is not set, a complicated algorithm is used to figure out the top of the working tree based on the value of GIT_DIR, and this can sometimes figure out that you are in a subdirectory of the working tree. In such a case, you are in the working tree, but not necessarily at the top. * Otherwise, commands that require to have working tree now barf. Earlier they always and consistently treated that your $cwd is the top of working tree and did not barf. This new world order is probably an improvement, and if the rules were like this from the beginning, it would have been much nicer. However, this _is_ a change of semantics in the middle of the road, and probably we will see many fallouts like this. Unfortunate... I am torn between a cleaner semantics and the short-term pain... - 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
