summaryrefslogtreecommitdiff
path: root/copy.c
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2014-09-02 13:20:12 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-09-02 13:20:13 -0700
commitc518279c0efbee88c31bb9916572ddfd9ac8eb00 (patch)
treefebace945b65c5666af2404c1410242509eb2eb9 /copy.c
parentMerge git://github.com/git-l10n/git-po (diff)
parentlockfile: allow reopening a closed but still locked file (diff)
downloadtgif-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 'copy.c')
0 files changed, 0 insertions, 0 deletions