undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

builtin/apply: remove misleading comment on lock_file field

Browse Source 
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>
This commit is contained in:
Junio C Hamano 2016-06-06 13:11:02 -07:00
parent a1bc3dd464
commit a7d4c49a82
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
builtin/apply.c
View File

@ -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;