summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar TroisSinges <TroisSinges@web>2013-11-26 15:35:42 +0000
committerGravatar admin <admin@branchable.com>2013-11-26 15:35:42 +0000
commit34baa822da94465b70d11c941f60e93809e3ac4c (patch)
tree8475b8b94d781fa7142a79fe8ab2f95b0b282ab1
parentc87e1cdeb24b43ad10e643c3d44404ce9fd800bf (diff)
-rw-r--r--doc/forum/Best_way_to_re-add_a_file_in_a_direct_and_crippled_annex_repository.mdwn17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/forum/Best_way_to_re-add_a_file_in_a_direct_and_crippled_annex_repository.mdwn b/doc/forum/Best_way_to_re-add_a_file_in_a_direct_and_crippled_annex_repository.mdwn
new file mode 100644
index 000000000..c126f8373
--- /dev/null
+++ b/doc/forum/Best_way_to_re-add_a_file_in_a_direct_and_crippled_annex_repository.mdwn
@@ -0,0 +1,17 @@
+Hi!
+
+What is the best way to add again the content of file in an direct and crippled annex repository? I'm using such a repository on a SMB drive, with no symbolic links, that's why the repository is in direct mode.
+
+For example:
+
+`/disk/annex-rep/a.bin` contains the text `../.git/annex/objects/W3/M8/SHA256E-s4701522386--e486cce01b1870cee394a376a3acc64a608e84e38b85e6c21c29721cf14328e6.bin/SHA256E-s4701522386--e486cce01b1870cee394a376a3acc64a608e84e38b85e6c21c29721cf14328e6.bin`
+
+and I've got the real content in another directory, outside annex: /disk/a.bin (contains the binary data)
+
+I imagined this process:
+* replace `/disk/annex-rep/a.bin` with `/disk/a.bin``
+* update `git-annex:122/4b8/SHA256E-s4701522386--e486cce01b1870cee394a376a3acc64a608e84e38b85e6c21c29721cf14328e6.bin.log` by adding this repository uuid
+
+I tried `git annex reinject` but it didn't work.
+
+Is there another way?