Re: [PATCH] Support ent:relative_path

From: Junio C Hamano <junkio@cox.net>
Date: May 5, 2007, 01:15 UTC
Message-ID: <7vtzusoyty.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <56b7f5510705041752o74b59284x872480e4413f83ab@mail.gmail.com>

"Dana How" <danahow@gmail.com> writes:

Show 16 quoted lines

> On 5/4/07, Junio C Hamano <junkio@cox.net> wrote:
>> Jakub Narebski <jnareb@gmail.com> writes:
>> > I'm not sure about "<tree-ish>:<path>" with <path> being relative by
>> > default. For me it is <path> in <tree-ish> (like in
>> > "git-ls-tree -r <tree-ish>" result).
>>
>> That's right (and Dscho is also).
>>
>> "v1.5.1:git.c" IS "git.c that appears at the toplevel of
>> v1.5.1's tree."
>>
>> Ok, for now let's forget about this relative stuff.
>
> Hmm, most of the work I do in the parts of our
> perforce repository I want to convert to git is
> far enough down...

The key word in my statement is "for now". I simply declared that I do not want to think about it further until 1.5.2 final, that's all.

I am not opposed to give an escape hatch for your problem; I am quite in favor of that, and I think Alex/J6t's "./" syntax is a reasonable compromise.