From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 6 Jun 2016 20:11:02 +0000 (-0700)
Subject: builtin/apply: remove misleading comment on lock_file field
X-Git-Tag: v2.10.0-rc0~190^2
X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/a7d4c49a8201f75699bf59852ef8e345f41a12b6

builtin/apply: remove misleading comment on lock_file field

Just like pointer field like prefix, the piece of memory pointed at
by lock_file field is not owned by the apply_state structure.  It is
true that the caller needs to be careful about the lifetime rule for
lockfile instances, but that is none of this API's business.

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

diff --git a/builtin/apply.c b/builtin/apply.c
index 7338ee6b68..b3eb704725 100644
--- a/builtin/apply.c
+++ b/builtin/apply.c
@@ -52,10 +52,7 @@ struct apply_state {
 	const char *prefix;
 	int prefix_length;
 
-	/*
-	 * Since lockfile.c keeps a linked list of all created
-	 * lock_file structures, it isn't safe to free(lock_file).
-	 */
+	/* These are lock_file related */
 	struct lock_file *lock_file;
 	int newfd;