summaryrefslogtreecommitdiff
path: root/CHANGELOG.md
diff options
context:
space:
mode:
authorCarlos Martín Nieto <cmn@dwim.me>2015-07-12 19:08:06 +0200
committerCarlos Martín Nieto <cmn@dwim.me>2015-07-12 19:08:06 +0200
commit01d0c02dbaa8856c4e2481ab1435bdf7df58690a (patch)
treecdf29c50e924cca1ba4f764a5fb7809cf9bfba67 /CHANGELOG.md
parenta522d8c1e72b3875805750cba9556fd303b9c8b2 (diff)
downloadlibgit2-01d0c02dbaa8856c4e2481ab1435bdf7df58690a.tar.gz
refdb: delete a ref's reflog upon deletioncmn/reflog-del-backend
Removing a reflog upon ref deletion is something which only some backends might wish to do. Backends which are database-backed may wish to archive a reflog, log-based ones may not need to do anything.
Diffstat (limited to 'CHANGELOG.md')
-rw-r--r--CHANGELOG.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c0a819ed7..243b696d7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -15,6 +15,10 @@ v0.23 + 1
* `git_cert` descendent types now have a proper `parent` member
+* It is the responsibility fo the refdb backend to decide what to do
+ with the reflog on ref deletion. The file-based backend must delete
+ it, a database-backed one may wish to archive it.
+
v0.23
------