Re: git bug? + question

From: Junio C Hamano <junkio@cox.net>
Date: Nov 3, 2006, 19:53 UTC
Message-ID: <7v7iyc71dt.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0611030741530.25218@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:

Show 6 quoted lines

> On Fri, 3 Nov 2006, Junio C Hamano wrote:
>> 
>> 	[remote."gitster"]
>
> Btw, why the '.'? It doesn't even work with a dot, you have to have a 
> space, which is also a lot more readable..

Untested example ;-).

I do not have to use any of these in real life because I work in repositories laid out without separate remotes.

Show 5 quoted lines

> This would basically require that "git-parse-remote" be re-written as a 
> native builtin, because quite frankly, it would be too damn painful any 
> other way, but it really shouldn't be that nasty. In fact, I think we 
> should have done that long ago, because the shell-code is just horrid for 
> things like this.

I agree.

I am rediscovering git-cvsimport and git-cvsexportcommit right now, and one thing I wished was git-cvsimport to have worked as if it is a git-fetch of an exotic flavor. Integrating it into git-fetch so that "URL: cvs://repo.si.to/ry" in .git/remotes would do a sensible thing and make git-cvsimport honor "Pull: HEAD:remotes/cvs/master" would both need some work in parse-remote, and doing anything more complicated than the current parse-remote in shell is quite painful.