From: Junio C Hamano Date: Thu, 10 May 2007 08:35:18 GMT Subject: Re: [PATCH 1/3] Move remote parsing into a library file out of builtin-push. Message-ID: <7v7irhkreh.fsf@assigned-by-dhcp.cox.net> In-Reply-To: Daniel Barkalow writes: > ..., "./gitcvs.git" would work (in the odd case where you actually have a > bare repository sitting in your working directory), ... This is a bit of tangent, because it does not change the issue we are discussing, and I suspect you already know this. But to avoid future confusion by people on the list who read this in the archive... "foo.git" does _NOT_ mean the directory is a bare repository. It is perfectly normal to have "foo.git/" that has a working tree whose repository data lives in "foo.git/.git". I _think_ (meaning, I haven't polled the userbase) requiring '/' may not break people's existing setup too badly, while it _is_ a regression in the sense that we suddenly start disallowing something we allowed for a long time, perhaps without no apparent good reason. I hope you'll correct me about "without no apparent good reason" part, which was what I was asking in my previous message. With a good rationale, it is much easier to sell a change that is a regression in the strictest sense but is unlikely to hurt people in practice.