Re: Suggestion: better error message when an ambiguous checkout is executed

2017-09-11 Thread Junio C Hamano
Junio C Hamano writes: > Mahmoud Al-Qudsi writes: > >> The default git behavior when attempting to `git checkout xxx` for >> some value of "xxx" that cannot be resolved to a single, unique >> file/path/branch/tag/commit/etc is to display the following: > ... > So a possible implementation approa

Re: Suggestion: better error message when an ambiguous checkout is executed

2017-08-07 Thread Junio C Hamano
Mahmoud Al-Qudsi writes: > The default git behavior when attempting to `git checkout xxx` for > some value of "xxx" that cannot be resolved to a single, unique > file/path/branch/tag/commit/etc is to display the following: > >> error: pathspec 'xxx' did not match any file(s) known to git Yes, it

Suggestion: better error message when an ambiguous checkout is executed

2017-08-07 Thread Mahmoud Al-Qudsi
Hello, The default git behavior when attempting to `git checkout xxx` for some value of "xxx" that cannot be resolved to a single, unique file/path/branch/tag/commit/etc is to display the following: > error: pathspec 'xxx' did not match any file(s) known to git Unfortunately, this is (IMHO) at b