summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment b/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment
index f6c6e5f4f..5cc9dc678 100644
--- a/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment
+++ b/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment
@@ -22,6 +22,7 @@ It seems that git is looking at `$PWD` to get "/hd/repo" and normalizing
the relative path via that. So there's no possible relative path
that git will accept in this situation. This kind of seems like buggy
behavior on git's part. I've posted about it to the git mailing list.
+<https://marc.info/?l=git&m=151008314122623&w=2>
git-annex could avoid the problem by not using relative paths of course,
but there are reasons including shorter path length (generally)