diff options
| author |  Junio C Hamano <gitster@pobox.com> | 2014-09-02 13:20:12 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2014-09-02 13:20:13 -0700 |
| commit | c518279c0efbee88c31bb9916572ddfd9ac8eb00 (patch) | |
| tree | febace945b65c5666af2404c1410242509eb2eb9 | |
| parent | Merge git://github.com/git-l10n/git-po (diff) | |
| parent | lockfile: allow reopening a closed but still locked file (diff) | |
| download | tgif-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
| -rw-r--r-- | cache.h | 1 | ||||
| -rw-r--r-- | lockfile.c | 10 |
2 files changed, 11 insertions, 0 deletions
@@ -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); diff --git a/lockfile.c b/lockfile.c index 2564a7f544..2a800cef33 100644 --- a/lockfile.c +++ b/lockfile.c @@ -237,6 +237,16 @@ int close_lock_file(struct lock_file *lk) return close(fd); } +int reopen_lock_file(struct lock_file *lk) +{ + if (0 <= lk->fd) + die(_("BUG: reopen a lockfile that is still open")); + if (!lk->filename[0]) + die(_("BUG: reopen a lockfile that has been committed")); + lk->fd = open(lk->filename, O_WRONLY); + return lk->fd; +} + int commit_lock_file(struct lock_file *lk) { char result_file[PATH_MAX]; |