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>
Junio C Hamano committed
Jun 6, 2016 at 13:11 UTC
a7d4c49a8201f75699bf59852ef8e345f41a12b6
1 file changed
+1
-4
builtin/apply.c
+1
-4
@@ -52,10 +52,7 @@ struct apply_state {
52
const char *prefix;
53
int prefix_length;
54
55
- /*
56
- * Since lockfile.c keeps a linked list of all created
57
- * lock_file structures, it isn't safe to free(lock_file).
58
- */
55
+ /* These are lock_file related */
56
struct lock_file *lock_file;
57
int newfd;
58