diff options
author | Martin Ågren <martin.agren@gmail.com> | 2017-10-05 22:32:10 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-10-06 10:07:18 +0900 |
commit | d13cd4c92760d8fe01fb51fbab556a4d1f3713b4 (patch) | |
tree | 0e75e587035287c7875387a157826cac74ec6677 /apply.h | |
parent | 6d058c882643dc45c8d708be98e86c38f25511a9 (diff) | |
download | git-d13cd4c92760d8fe01fb51fbab556a4d1f3713b4.tar.gz |
apply: remove `newfd` from `struct apply_state`
Similar to a previous patch, we do not need to use `newfd` to signal
that we have a lockfile to clean up. We can just unconditionally call
`rollback_lock_file`. If we do not hold the lock, it will be a no-op.
Where we check `newfd` to decide whether we need to take the lock, we
can instead use `is_lock_file_locked()`.
Signed-off-by: Martin Ågren <martin.agren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'apply.h')
-rw-r--r-- | apply.h | 3 |
1 files changed, 1 insertions, 2 deletions
@@ -36,9 +36,8 @@ enum apply_verbosity { struct apply_state { const char *prefix; - /* These are lock_file related */ + /* Lock file */ struct lock_file lock_file; - int newfd; /* These control what gets looked at and modified */ int apply; /* this is not a dry-run */ |