"Philip Oakley" <philipoakley@xxxxxxx> writes: > From: "Junio C Hamano" <gitster@xxxxxxxxx> >> "Philip Oakley" <philipoakley@xxxxxxx> writes: >> >>> ... and the detection process for 'toplevel' may not work >>> properly when in a separated work-tree environment. >> >> Without GIT_WORK_TREE exported to point at the top-level, there is >> nothing that lets us "detect" it, as the working tree does not have >> ".git" directory to tell us to stop, no? >> > > "No", but not in that way. > > My point (to Dale) was, as you state, that the "cd to top level" was > (IIUC) the probable causes of the fault, and that a documentation > update would probably be appropriate for the discussion on exporting > GIT_WORK_TREE, and that it would specifically mention those git > commands that needed to "cd to top level", and hence would not work in > such an environment. (I wasn't sure where the appropriate "cd to top > level" function was) > > An explanation here on the list wouldn't solve the problems for others > who are yet to make the same mistake, hence the implied suggestion. I understand what you mean by these last two lines. It was unclear to me which part of our documentation needs updating and how, and that was (and still is) what I was primarily interested in finding out. -- 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