From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 13 Jan 2009 05:37:05 GMT
Subject: Re: [PATCH] Simple update to bash completions to prevent unbound variable errors.
Message-ID: <7vr637epha.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <496C18D8.9070707@tedpavlic.com>

Ted Pavlic <ted@tedpavlic.com> writes:

>>> +# __gitcomp_1 requires 2 arguments
>>
>> ... and $1 and $2 mean?
>
> No clue. Patches are welcome.

To be absolutely honest, I think people with "set -u" in their interactive
environment are sick.  Bourne shells have been substituting unset
variables to empty string for eons, and this is not _my_ itch to scratch.

It seems to be yours, though, and I was merely trying to help.