Re: Doesn't disambiguate between 'external command failed' and 'command not found'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeff King <peff@xxxxxxxx> writes:

> I'm not all that happy with the advice, though. It's pretty technical
> and specific. I'm not sure whether it would be helpful to most users or
> not.

Yeah, Michael's rewording makes it fuzzier by saying "exists, unable to
execute, maybe git-%s is broken?".

I notice that we do not give the path to the file that implements the
command. Perhaps we should walk the $PATH after we see this failure to
pinpoint which one is to be inspected (I vaguely recall a weatherbaloon
patch to a similar effect)?

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]