From: rsbecker@nexbridge.com
Date: Mon, 09 Sep 2024 19:28:52 GMT
Subject: RE: [bug?] git diff --cached in a non-git directory
Message-ID: <05e201db02ee$84787380$8d695a80$@nexbridge.com>
In-Reply-To: <xmqqy140pt67.fsf@gitster.g>

On September 9, 2024 2:40 PM, Junio C Hamano wrote:
><rsbecker@nexbridge.com> writes:
>
>>>error: unknown option `cached'
>>>usage: git diff --no-index [<options>] <path> <path> [...]
>> ...
>> Because you are not in a git repository clone, the --cached option has
>> no meaning.
>
>Yes.  "git diff" unfortunately has a mode where a limited subset of its
features is
>available and that is called the "--no-index" mode.
>
>Because the command is capable of working outside a repository, "You are
not in a
>repository" is a not a good error message in this situation, either.  It is
not that you
>stepped outside a repository that is your error.  It is not that you used
"--cached"
>that is your error, either.  You used "--cached" outside a repository, that
is where
>your error is.
>
>A patch to improve the error messages in such a situation is certainly
welcome.

Glad to. Can you point me at where this is generated?