summaryrefslogtreecommitdiff
path: root/CHANGELOG.md
diff options
context:
space:
mode:
authorCarlos Martín Nieto <cmn@dwim.me>2015-09-05 03:54:06 +0200
committerCarlos Martín Nieto <cmn@dwim.me>2015-09-05 16:43:49 +0200
commitd83b2e9f51539287d5d2b1bd939ea9540fa6e5be (patch)
treee031e903e55e68ca45df30bdeb8c348b112835d3 /CHANGELOG.md
parent1cef6b9f190587a78c65bd3168879be3eb37e0fb (diff)
downloadlibgit2-d83b2e9f51539287d5d2b1bd939ea9540fa6e5be.tar.gz
filebuf: follow symlinks when creating a lock filecmn/follow-symlink
We create a lockfile to update files under GIT_DIR. Sometimes these files are actually located elsewhere and a symlink takes their place. In that case we should lock and update the file at its final location rather than overwrite the symlink.
Diffstat (limited to 'CHANGELOG.md')
-rw-r--r--CHANGELOG.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8f28cbf3b..1f3c3ed6f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,9 @@ v0.23 + 1
example `filter=*`. Consumers should examine the attributes parameter
of the `check` function for details.
+* Symlinks are now followed when locking a file, which can be
+ necessary when multiple worktrees share a base repository.
+
### API additions
* `git_config_lock()` has been added, which allow for