From: Junio C Hamano Date: Thu, 10 May 2007 08:21:16 GMT Subject: Re: [PATCH 1/3] Move remote parsing into a library file out of builtin-push. Message-ID: <7virb1ks1v.fsf@assigned-by-dhcp.cox.net> In-Reply-To: Daniel Barkalow writes: >> And I think it does today. > > Hmm, and I guess URIs on the command line work the same way. How about > requiring a '/' somewhere in a repository argument in order to treat it as > a repository instead of a remote name? Then "../next-door-neighbour" would > work, "./gitcvs.git" would work (in the odd case where you actually have a > bare repository sitting in your working directory), but we'd avoid the > current default of pushing to a bare repository in "./origin/" if nothing > at all is configured. When I wrote the message you are responding to, I thought this was a regression from the current behaviour, which (IIRC--it's getting late and I am tired to double check) essentially says if the token is a name of the directory, the target repository is a local one, but "we'd avoid..." part seems to suggest that you actually did this deliberately as a fix to some problem in the current behaviour. I am not however sure what it exactly is. Could you care to elaborate the part after "we'd avoid..." to clarify what the problem is, please?