From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 25 Feb 2009 21:25:09 GMT
Subject: Re: [PATCH 2/2] git submodule: Fix adding of submodules at paths with ./
Message-ID: <7v7i3e1a6i.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <49A541D3.4030001@viscovery.net>

Johannes Sixt <j.sixt@viscovery.net> writes:

> Michael J Gruber schrieb:
> ...
>> Now, the /// are in fact a valid concern[1], although probably not that
>> common an isue.
>
> I'm fine if only common use cases are taken care of. If you say that ./ is
> common and /// is not, then I'll believe it because I'm not a git
> submodule user (yet) and can't argue about this with my own experience.

Even if it is not worth the complication to the code to fix /// or /../
cases, I think it is worth *detecting* such an incoming path and error
out, telling the user not to give a "funky" path.