On 8/22/2023 3:45 PM, Junio C Hamano wrote:
> "Derrick Stolee via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes:
>> + switch (discover_git_directory_reason(&commondir, &gitdir)) {
>> + case GIT_DIR_INVALID_OWNERSHIP:
>> + warning(_("repository at '%s' has different owner"), dir);
>> + goto loop_end;
>> +
>> + case GIT_DIR_DISCOVERED:
>> + succeeded = 1;
>> + break;
>> +
>> + default:
>> + warning(_("repository not found in '%s'"), dir);
>> + break;
>
> Among the error cases, INVALID_OWNERSHIP is one of the possibilities
> that merits specialized message to the end-user. I wonder if others
> also deserve to be explained, though.
The specific choice of GIT_DIR_INVALID_OWNERSHIP is singled out
because it's a new-ish reason and is the most confusing to users
when things fail for this reason.
> - HIT_CEILING and HIT_MOUNT_POINT will happen when there is no
> usable repository between "dir" and the specified ceiling.
These are basically "didn't find a Git repo" but there are different
reasons why Git stopped looking. I'm not sure there is something more
valuable to indicate here than the "repository not found" message
that already exists.
> - INVALID_GITFILE and INVALID_FORMAT are signs of some repository
> corruption.
I can add a message for this kind of error, which seems helpful to
point out to a user.
> - DISALLOWED_BARE is unlikely to happen in the scalar context.
I agree.
Thanks,
-Stolee
