summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-07-07 19:29:36 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-07-07 19:29:36 -0400
commit67dcc1f171f0bbe2b57d20fbafce9f6c9b8f781e (patch)
tree023171ff974e670cf3951033514f86d5b371a654 /doc
parentff531b96778abba9e992103a644ba80f7ddf2397 (diff)
add: Avoid a failure mode that resulted in the file seemingly being deleted (content put in the annex but no symlink present).
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn
index af807b65d..d17e569f1 100644
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn
+++ b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn
@@ -8,3 +8,7 @@ Recently I ran into the following situation under Ubuntu with an encrypted home
The file seems to be completely gone. It no longer exists in the current directory, or under .git/annex.
I don't mind horribly that git-annex failed due to the name length limit, but it shouldn't have deleted my file in the process (fortunately the file wasn't very important, or hard to recover).
+
+> [[done]], as noted it did not delete content and now it makes the symlink
+> before trying to write to the location log, avoiding that gotcha.
+> --[[Joey]]