Re: [PATCH] Simple support for tree entry specification with relative pathnames

From: Alex Riesen <raa.lkml@gmail.com>
Date: Dec 18, 2007, 21:17 UTC
Message-ID: <20071218211713.GG2875@steel.home>
In-Reply-To: <56b7f5510712181303h1e7ae35dpa0adfd6804a7cecd@mail.gmail.com>

Dana How, Tue, Dec 18, 2007 22:03:04 +0100:

> ACK from me...

But NAK from me. Definitely not in this form. Please consider the patches *only* as an RFC.

> I submitted a similar patch last May 4 which also changed
> sha1_name.c to do this.  The patch added a config variable to
> control this (probably not desirable).  The patch also handled
> leading/embedded . and .. .

This one (the last in series) too.

Show 8 quoted lines

> In p4 you can say
>   p4 <operation> file#rev
> and file is interpreted relatively.
> 
> I wanted to be able to say
>   git <operation> tree:file
> and have file interpreted relatively.
> This should only happen when you are inside the work tree.

It is pure coincedence the syntaxes look similar. They are very deeply different in Git and Perforce.