summaryrefslogtreecommitdiff
path: root/streaming.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2013-07-07 10:03:29 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-07-07 17:50:13 (GMT)
commit7c07385d902f6d8c177d533dc2faa36ef4a52a66 (patch)
treef4b7fb51d940c2fcec6cc1e238beb7641f564335 /streaming.c
parentedca4152560522a431a51fc0a06147fc680b5b18 (diff)
downloadgit-7c07385d902f6d8c177d533dc2faa36ef4a52a66.zip
git-7c07385d902f6d8c177d533dc2faa36ef4a52a66.tar.gz
git-7c07385d902f6d8c177d533dc2faa36ef4a52a66.tar.bz2
zero-initialize object_info structs
The sha1_object_info_extended function expects the caller to provide a "struct object_info" which contains pointers to "query" items that will be filled in. The purpose of providing pointers rather than storing the response directly in the struct is so that callers can choose not to incur the expense in finding particular fields that they do not care about. Right now the only query item is "sizep", and all callers set it explicitly to choose whether or not to query it; they can then leave the rest of the struct uninitialized. However, as we add new query items, each caller will have to be updated to explicitly turn off the new ones (by setting them to NULL). Instead, let's teach each caller to zero-initialize the struct, so that they do not have to learn about each new query item added. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'streaming.c')
-rw-r--r--streaming.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/streaming.c b/streaming.c
index cabcd9d..cac282f 100644
--- a/streaming.c
+++ b/streaming.c
@@ -135,7 +135,7 @@ struct git_istream *open_istream(const unsigned char *sha1,
struct stream_filter *filter)
{
struct git_istream *st;
- struct object_info oi;
+ struct object_info oi = {0};
const unsigned char *real = lookup_replace_object(sha1);
enum input_source src = istream_source(real, type, &oi);