summaryrefslogtreecommitdiff
path: root/contrib/coccinelle/object_id.cocci
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2019-01-07 08:37:02 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-01-08 17:40:19 (GMT)
commit00a7760e81e067cdfb6113e02d141d508529ffc7 (patch)
tree2ae7c4aa7d1c5964f517ea93c06ad10f7750667a /contrib/coccinelle/object_id.cocci
parent514c5fdd03b914c72a91bb420e46bdc8886940cf (diff)
downloadgit-00a7760e81e067cdfb6113e02d141d508529ffc7.zip
git-00a7760e81e067cdfb6113e02d141d508529ffc7.tar.gz
git-00a7760e81e067cdfb6113e02d141d508529ffc7.tar.bz2
sha1-file: modernize loose header/stream functions
As with the open/map/close functions for loose objects that were recently converted, the functions for parsing the loose object stream use the name "sha1" and a bare "unsigned char *". Let's fix that so that unpack_sha1_header() becomes unpack_loose_header(), etc. These conversions are less clear-cut than the file access functions. You could argue that the they are parsing Git's canonical object format (i.e., "type size\0contents", over which we compute the hash), which is not strictly tied to loose storage. But in practice these functions are used only for loose objects, and using the term "loose_header" (instead of "object_header") distinguishes it from the object header found in packfiles (which contains the same information in a different format). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/coccinelle/object_id.cocci')
0 files changed, 0 insertions, 0 deletions