summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/devblog/day_392__v6_fixes/comment_2_15434848be1951e93a1e5b9fcbccedb0._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/devblog/day_392__v6_fixes/comment_2_15434848be1951e93a1e5b9fcbccedb0._comment b/doc/devblog/day_392__v6_fixes/comment_2_15434848be1951e93a1e5b9fcbccedb0._comment
new file mode 100644
index 000000000..129f88e98
--- /dev/null
+++ b/doc/devblog/day_392__v6_fixes/comment_2_15434848be1951e93a1e5b9fcbccedb0._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2016-05-21T13:55:01Z"
+ content="""
+Dangling objects are not related to the v6 syncing problems mentioned in
+this post.
+
+You can generally safely delete dangling objects from a git repository;
+git gc does it automatically after 30 days or so. git-annex does not
+normally create dangling objects but several git operations can.
+"""]]