Re: [PATCH] grep: --full-tree

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 26, 2009, 00:36 UTC
Message-ID: <7vd436m8af.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4B0DCC27.4030702@gmail.com>

A Large Angry SCM <gitzilla@gmail.com> writes:

Show 24 quoted lines

> Junio C Hamano wrote:
>> A Large Angry SCM <gitzilla@gmail.com> writes:
>>
>>> But the users are almost always dealing with things (objects) that
>>> started as files, act like files and may be files again. Why should
>>> they not expect filesystem semantics.
>>
>> Do you truly want to see this?
>>
>>     diff --git a/var/tmp/git/Makefile b/var/tmp/git/Makefile
>>     index 5a0b3d4..e9b03a8 100644
>>     --- a/var/tmp/git/Makefile
>>     +++ b/var/tmp/git/Makefile
>>     @@ -1985,3 +1985,4 @@ coverage-report:
>>     ...
>>
>> As long as you are talking about paths you communicate with git, your
>> root _is_ the root of the work tree, and it shouldn't matter where you
>> have your work tree.
>>
>> That is what I meant by "the root _in the context_".
>
> Nice example for a command output. But what did the user specify on
> the command line?

Either relative path from $(cwd) or full pathname from the root of the filesystem in your world (because you do not understand the value of the context), and ralative path from $(cwd) or full pathname from the root of the work tree in my world.