From: Steffen Prohaska <prohaska@zib.de>
Date: Wed, 15 Aug 2007 13:06:58 GMT
Subject: Re: git on Cygwin: Not a valid object name HEAD
Message-ID: <3F9AF722-0610-4778-A244-DBE5A0918D0B@zib.de>
In-Reply-To: <30e4a070708150548r3234cd66yd4ee6a85989a98b1@mail.gmail.com>


On Aug 15, 2007, at 2:48 PM, Mark Levedahl wrote:

> On 8/15/07, Mark Levedahl <mlevedahl@gmail.com> wrote:
>> On 8/15/07, Shawn O. Pearce <spearce@spearce.org> wrote:
>>> David Kastrup <dak@gnu.org> wrote:
>>>>     Load a Hive, Query, Save, Restore, and Unload a Hive. To  
>>>> install
>>>>     the Support Tools:
>>>>
>>>>     1.
>>>>
>>>>
>>>>     Insert the Windows 2000 CD-ROM into your CD-ROM drive.
>>>
>>> Indeed, that step right there will stop many users cold in their
>>> tracks.
>>
> maybe something like ...
>
> case "$(uname -s) in
>    MSYS*)
>        <your way>;;
>    *)
>        <the unix way>;;
> esac

If reg.exe is not there kdiff3 will not be found. The code will
already be _ignored_. It's just not working.

It may make sense to use 'uname -s' to explicitly control that the
code is expected to work. This would allow to report errors if a
command is missing. However, cluttering all shell scripts with
uname's will likely become quite confusing.

If performance is a concern, we may execute uname -s only once
in git-sh-setup and assign its return to something like GIT_UNAME.
This may save us a few forks, which are to my knowledge quite
expensive on Windows.

	Steffen