Matthias Lederhofer <matled@xxxxxxx> writes: > Thanks. I'll have a look at receive-pack this week. Is there > anything in receive-pack yet which helps to use a working tree in the > hooks? Or is this something for which the behaviour of git still has > to be defined? I think the behaviour for receive-pack and the environment the hooks run in have been pretty well defined. You start in the repository (the directory $GIT_DIR), GIT_DIR is set and points at it. The issue is that the introduction of WORK_TREE enviornment and core.worktree mechanism might want to update the semantics. For example, some people seem to run checkout (or perhaps "merge") to update the associated working tree. Can they find out where the root of the working tree is (because they would want to chdir to it before saying "git checkout"), given the current environment receive-pack sets up for them? Earlier we said that people who use only GIT_DIR without GIT_WORK_TREE nor core.worktree should get exactly the same semantics with or without the WORK_TREE topic, so the above may not be an issue. - 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
