From: Perry Wagle <wagle@cs.indiana.edu>
Date: Thu, 28 Aug 2008 23:28:34 GMT
Subject: Re: [kernel.org users] [RFD] On deprecating "git-foo" for builtins
Message-ID: <76E64CE4-758C-4215-BA46-A222A8D78C12@cs.indiana.edu>
In-Reply-To: <7vmyiwd8ot.fsf@gitster.siamese.dyndns.org>

My (ahem) implied point (sorry) also was that these "hook" scripts act  
as examples of how to write git scripts in general, and some of them  
are written to me run as regular scripts.

-- Perry

On Aug 28, 2008, at 4:24 PM, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
>
>>> In March 2008, the sample git-hooks and git-web used git<DASH>  
>>> commands.
>>> That was the last I looked at git until Tuesday of this week.
>>
>> Yes, and some of the test scripts still have git-* in them. I think  
>> in
>> that respect, the git community has been very bad about eating our  
>> own
>> dog food.
>
> Not at all.
>
> For one thing, hooks do run under modified PATH, as already pointed  
> out in
> the earlier thread.
>
> Test scripts are executed in a special environment whose GIT_EXEC_PATH
> points at the top of the build tree, where all git-foo lives.
>
> Before anybody greps in Documentation/ to make pointless noises  
> about some
> dashed-form git-foo in there when we do not talk about what the user  
> types
> but about a command as a concept in manual pages, they are left in  
> dashed
> form deliberately, partly to help manpage browsers crosslink across  
> pages.
>
> We could have described typographic convention,
>
> Cf.
>
>    http://thread.gmane.org/gmane.comp.version-control.git/86940/focus=87008
>
> but we ended up not doing so.