From: Uwe Kleine-König Date: Fri, 10 Aug 2007 11:28:21 GMT Subject: Re: [PATCH] Reinstate the old behaviour when GIT_DIR is set and GIT_WORK_TREE is unset Message-ID: <20070810112821.GA11026@informatik.uni-freiburg.de> In-Reply-To: <7vr6mbu8iv.fsf_-_@assigned-by-dhcp.cox.net> Hello Junio, Junio C Hamano wrote: > From: Johannes Schindelin > Date: Sun, 5 Aug 2007 14:12:53 +0100 > > The old behaviour was to unilaterally default to the cwd is the work tree > when GIT_DIR was set, but GIT_WORK_TREE wasn't, no matter if we are inside > the GIT_DIR, or if GIT_DIR is actually something like ../../../.git. > > Signed-off-by: Johannes Schindelin > Signed-off-by: Junio C Hamano > --- > > Johannes Schindelin writes: > > > I think I sent a patch for that, but was negative about it, even if I > > promised not to question your decision. > > Yes you did. Here is a refresher with an affected test > adjusted. > > We already have a few changes that worked around the semantics > change by either setting GIT_WORK_TREE or cd'ing up, but I > think they should not need to be reverted. > > It makes more sense to keep the old semantics -- people who use > unusual GIT_DIR setting should know what they are doing, and > the new GIT_WORK_TREE feature (and core.worktree) would give > them better control. We just should not break existing users > that set GIT_DIR and nothing else. Which means I need another > rewrite on the Release Notes, and probably yet another rc > cycle. I don't know if you planed to make git checkout-index --prefix=/tmp/tra -a work (again) in a bare repo. Probably not, so it's no surprise that it still doesn't work. Best regards Uwe -- Uwe Kleine-König cat /*dev/null; echo 'Hello World!'; cat > /dev/null <<*/ () { } int main() { printf("Hello World!\n");} /* */