summaryrefslogtreecommitdiff
path: root/Documentation/git-log.txt
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2014-07-14 10:29:58 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-07-14 13:05:37 -0700
commit93dcaea22674864f931be3fe6050671d335dc5b0 (patch)
tree766396abcc4aba5fa2ac49aec1ff5b5cd11bb7e3 /Documentation/git-log.txt
parentt1700: new tests for split-index mode (diff)
downloadtgif-93dcaea22674864f931be3fe6050671d335dc5b0.tar.xz
lockfile: allow reopening a closed but still locked file
In some code paths (e.g. giving "add -i" to prepare the contents to be committed interactively inside "commit -p") where a caller takes a lock, writes the new content, give chance for others to use it while still holding the lock, and then releases the lock when all is done. As an extension, allow the caller to re-update an already closed file while still holding the lock (i.e. not yet committed) by re-opening the file, to be followed by updating the contents and then by the usual close_lock_file() or commit_lock_file(). This is necessary if we want to add code to rebuild the cache-tree and write the resulting index out after "add -i" returns the control to "commit -p", for example. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-log.txt')
0 files changed, 0 insertions, 0 deletions