summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar helmut <helmut@web>2013-12-02 18:24:13 +0000
committerGravatar admin <admin@branchable.com>2013-12-02 18:24:13 +0000
commitbbb532c571782a0898974657ed820da376a85658 (patch)
tree5ef78746a46c910b15536976ca0bae2483124a94 /doc
parenta774d44d452d77d088f1c92cd4af6585c7b4020f (diff)
Added a comment: git as a database
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_2_a8bb264cb2ceece72e0dd9191b2b566e._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_2_a8bb264cb2ceece72e0dd9191b2b566e._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_2_a8bb264cb2ceece72e0dd9191b2b566e._comment
new file mode 100644
index 000000000..ec921ce8f
--- /dev/null
+++ b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_2_a8bb264cb2ceece72e0dd9191b2b566e._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="helmut"
+ ip="89.0.78.89"
+ subject="git as a database"
+ date="2013-12-02T18:24:12Z"
+ content="""
+You said that \"[...] it will use more disk over time. Probably not the best choice.\" But this does not have to be true. Since this git ref is never synced, an update can be forced. The tricky part is in finding good truncation points. Now for fsck, the log can be truncated whenever an incremental fsck is started.
+"""]]