summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@g5.osdl.org>2005-07-04 04:01:11 (GMT)
committerLinus Torvalds <torvalds@g5.osdl.org>2005-07-04 04:01:11 (GMT)
commit671fe4bb20cf36b0f9de763b863425f5bea30c06 (patch)
tree4bdca3bd8333192d6fb8c98c82b6c74f70e6e0e9 /t
parent5736bef18c37e811f39bafb9895fee349fa7bbe6 (diff)
downloadgit-671fe4bb20cf36b0f9de763b863425f5bea30c06.zip
git-671fe4bb20cf36b0f9de763b863425f5bea30c06.tar.gz
git-671fe4bb20cf36b0f9de763b863425f5bea30c06.tar.bz2
git-rev-parse: support show sha1 names for pack entries
This is actually subtly wrong. If a short match is found in the object directory, but would _also_ match another SHA1 ID in a pack (or it shows in one pack but not another), we'll never have done the pack lookup, and we think it's unique. I can't find it in myself to care. You really want to use enough of a SHA1 that there is never any ambiguity.
Diffstat (limited to 't')
0 files changed, 0 insertions, 0 deletions