aboutsummaryrefslogtreecommitdiff
path: root/cache.h
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-09-02 13:20:12 -0700
committerJunio C Hamano <gitster@pobox.com>2014-09-02 13:20:13 -0700
commitc518279c0efbee88c31bb9916572ddfd9ac8eb00 (patch)
treefebace945b65c5666af2404c1410242509eb2eb9 /cache.h
parent96db324a73fdada6fbe7b63221986f8f18cc63b0 (diff)
parent93dcaea22674864f931be3fe6050671d335dc5b0 (diff)
downloadgit-c518279c0efbee88c31bb9916572ddfd9ac8eb00.tar.gz
git-c518279c0efbee88c31bb9916572ddfd9ac8eb00.tar.xz
Merge branch 'jc/reopen-lock-file'
There are cases where you lock and open to write a file, close it to show the updated contents to external processes, and then have to update the file again while still holding the lock, but the lockfile API lacked support for such an access pattern. * jc/reopen-lock-file: lockfile: allow reopening a closed but still locked file
Diffstat (limited to 'cache.h')
-rw-r--r--cache.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/cache.h b/cache.h
index fcb511db7..30268b6ee 100644
--- a/cache.h
+++ b/cache.h
@@ -585,6 +585,7 @@ extern NORETURN void unable_to_lock_index_die(const char *path, int err);
extern int hold_lock_file_for_update(struct lock_file *, const char *path, int);
extern int hold_lock_file_for_append(struct lock_file *, const char *path, int);
extern int commit_lock_file(struct lock_file *);
+extern int reopen_lock_file(struct lock_file *);
extern void update_index_if_able(struct index_state *, struct lock_file *);
extern int hold_locked_index(struct lock_file *, int);