summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar atrent <atrent@web>2015-11-16 09:06:34 +0000
committerGravatar admin <admin@branchable.com>2015-11-16 09:06:34 +0000
commit9625e733c59c5bf4e5c11b135480b67f0c1b9c77 (patch)
treea0c056822d5d8213dad8c33aadcfe4e0a6eb1424
parent67727a74004734d8a29e09ef0e186a8cd15373a2 (diff)
Added a comment
-rw-r--r--doc/tips/recover_data_from_lost+found/comment_3_02cb9efd54d8447d0bd11e5981e7dca7._comment13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/tips/recover_data_from_lost+found/comment_3_02cb9efd54d8447d0bd11e5981e7dca7._comment b/doc/tips/recover_data_from_lost+found/comment_3_02cb9efd54d8447d0bd11e5981e7dca7._comment
new file mode 100644
index 000000000..7121f380c
--- /dev/null
+++ b/doc/tips/recover_data_from_lost+found/comment_3_02cb9efd54d8447d0bd11e5981e7dca7._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="atrent"
+ subject="comment 3"
+ date="2015-11-16T09:06:34Z"
+ content="""
+This procedure is also very useful when you accidentally rename files in the object dir.
+
+Such a case occurred to me when I 'detoxed' a git-annex: detox renames files and it substitutes \"--\" with \"-\", thus destroying my annex.
+
+I find git-annex very elegant in this situation: rather than trying to rename back the files (objects) you just re-add them (since content is still there unmodified) recreating the symlink targets!
+
+Kudos!
+"""]]