From: Jon Forrest <nobozo@gmail•com>
To: git@vger•kernel.org
Subject: Minor Bug in git cat-file (git 2.50)?
Date: Sun, 10 Aug 2025 07:52:42 -0700 [thread overview]
Message-ID: <b37629c6-b730-45ce-b839-e782aafe238d@gmail.com> (raw)
(Sorry if you see this more than once)
I'm using 'git cat-file' to show the example. This is probably not a
command-specific problem.
The problem is that using a deliberately ambiguous object ID produces
surprising output. This is a minor issue.
% git --version
git version 2.50.GIT
% uname -a
Linux fedora 6.15.9-201.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Aug 2
11:37:34 UTC 2025 x86_64 GNU/Linux
% git init
# depending on where you run the test, might not be necessary
% git config --global --add safe.directory /tmp
Initialized empty Git repository in /tmp/.git/
% echo a > a.txt
% git add a.txt
% git ls-files -s
100644 78981922613b2afb6025042ff6bd878ac1994e85 0 a.txt
% git cat-file -t 78981922613b2afb6025042ff6bd878ac1994e85
blob
# All is well so far.
% pushd .git/objects/78
% ls
981922613b2afb6025042ff6bd878ac1994e85
# create a new file with the same name as the file that already exists,
# except change the final letter to something else.
% cp 981922613b2afb6025042ff6bd878ac1994e85
981922613b2afb6025042ff6bd878ac1994e86
% ls
981922613b2afb6025042ff6bd878ac1994e85
981922613b2afb6025042ff6bd878ac1994e86
% popd
# use an ambiguous SHA1 prefix
# why does the next command produce two identical hints, both of which
# are incorrect?
% git cat-file -t 78981922613b2afb6025042ff6bd878ac1994e8
error: short object ID 78981922613b2afb6025042ff6bd878ac1994e8 is
ambiguous # this is correct
hint: The candidates are:
hint: 7898192 blob
hint: 7898192 blob
fatal: Not a valid object name 78981922613b2afb6025042ff6bd878ac1994e8
# I would have expected:
hint: 78981922613b2afb6025042ff6bd878ac1994e85 blob
hint: 78981922613b2afb6025042ff6bd878ac1994e86 blob
# using the supplied hint doesn't work, which is no surprise
% git cat-file -t 7898192
fatal: Not a valid object name 7898192
Cordially,
Jon Forrest
next reply other threads:[~2025-08-10 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 14:52 Jon Forrest [this message]
2025-08-11 8:54 ` Minor Bug in git cat-file (git 2.50)? Patrick Steinhardt
2025-08-11 19:10 ` Jon Forrest
2025-08-11 15:09 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b37629c6-b730-45ce-b839-e782aafe238d@gmail.com \
--to=nobozo@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox