diff options
author | brian m. carlson <sandals@crustytoothpaste.net> | 2017-03-26 19:01:24 +0300 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-03-27 08:08:21 +0300 |
commit | dc01505f7f272a44b974e622f75bd592debe9dcb (patch) | |
tree | 7aa62babd604067a3d928edfa988391711a36007 /sha1_file.c | |
parent | 5028bf628c7ebfb85d14ec7dc296b264a1c3bcd3 (diff) |
Convert GIT_SHA1_HEXSZ used for allocation to GIT_MAX_HEXSZ
Since we will likely be introducing a new hash function at some point,
and that hash function might be longer than 40 hex characters, use the
constant GIT_MAX_HEXSZ, which is designed to be suitable for
allocations, instead of GIT_SHA1_HEXSZ. This will ease the transition
down the line by distinguishing between places where we need to allocate
memory suitable for the largest hash from those where we need to handle
the current hash.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'sha1_file.c')
-rw-r--r-- | sha1_file.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sha1_file.c b/sha1_file.c index 71063890ff..e763000d34 100644 --- a/sha1_file.c +++ b/sha1_file.c @@ -3759,7 +3759,7 @@ static int for_each_file_in_obj_subdir(int subdir_nr, strbuf_addf(path, "/%s", de->d_name); if (strlen(de->d_name) == GIT_SHA1_HEXSZ - 2) { - char hex[GIT_SHA1_HEXSZ+1]; + char hex[GIT_MAX_HEXSZ+1]; struct object_id oid; snprintf(hex, sizeof(hex), "%02x%s", |