parse_commit_buffer(): notice NUL in the commit buffer

It is unusual to have NUL byte appear anywhere in the commit object.
Leave a note in the commit object if we notice such a case while parsing
the buffer for structural information, so that codepaths that want to be
extra careful can inspect it further.

Signed-off-by: Junio C Hamano <gitster@pobox.com>

2 files changed, 5 insertions, 0 deletions

diff --git a/commit.c b/commit.c
index 73b7e00292..0f58471602 100644
--- a/commit.c
+++ b/commit.c
@@ -258,6 +258,7 @@ int parse_commit_buffer(struct commit *item, const void *buffer, unsigned long s
 	if (item->object.parsed)
 		return 0;
 	item->object.parsed = 1;
+	item->flags = memchr(buffer, '\0', size) ? COMMIT_HAS_NUL : 0;
 	tail += size;
 	if (tail <= bufptr + 46 || memcmp(bufptr, "tree ", 5) || bufptr[45] != '\n')
 		return error("bogus commit object %s", sha1_to_hex(item->object.sha1));
diff --git a/commit.h b/commit.h
index 009b113e5b..dd5e27802c 100644
--- a/commit.h
+++ b/commit.h
@@ -15,6 +15,10 @@ struct commit {
 	struct object object;
 	void *util;
 	unsigned int indegree;
+
+	unsigned flags;
+#define COMMIT_HAS_NUL       01
+
 	unsigned long date;
 	struct commit_list *parents;
 	struct tree *tree;