summaryrefslogtreecommitdiff
path: root/doc/tips
diff options
context:
space:
mode:
authorGravatar http://id.clacke.se/ <clacke@web>2013-11-12 16:17:42 +0000
committerGravatar admin <admin@branchable.com>2013-11-12 16:17:42 +0000
commit9355a6c835e3ee5b21ed76d4c932a8647dcb312e (patch)
treee2a12e720156e0be3c2c83a5fb2e7929da849589 /doc/tips
parent026a27ae89d9ac513cfe363fdf612d32fae618e2 (diff)
Added a comment
Diffstat (limited to 'doc/tips')
-rw-r--r--doc/tips/recovering_from_a_corrupt_git_repository/comment_3_11bece6dfac090edbcd783b266c482a3._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/tips/recovering_from_a_corrupt_git_repository/comment_3_11bece6dfac090edbcd783b266c482a3._comment b/doc/tips/recovering_from_a_corrupt_git_repository/comment_3_11bece6dfac090edbcd783b266c482a3._comment
new file mode 100644
index 000000000..63f443a31
--- /dev/null
+++ b/doc/tips/recovering_from_a_corrupt_git_repository/comment_3_11bece6dfac090edbcd783b266c482a3._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://id.clacke.se/"
+ nickname="clacke"
+ subject="comment 3"
+ date="2013-11-12T16:17:42Z"
+ content="""
+Luckily, so far the objects getting corrupted have been in past commits (maybe only in packfiles?), not the latest ones, so I have been able to recover even though HEAD has been unique to the local repo.
+"""]]