Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Assuming 3 commits
commit e824a9be48accc21da5907924a5f7a20c48447ed
commit 62f819bdfe38e6252a54f5aae47fbf150d4e3371
commit eb8f996f6797df717247f911040b7d597b386ec3
Why would git log 62f be thought of ambiguous?
fatal: ambiguous argument '62f': unknown revision or path not in the working tree.
After all, 62f uniquely identifies second commit
Git’s message is misleading here. Although
62fis not ambiguous, Git requires a short SHA1 to be at least four characters long.