summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2017-11-07 16:09:27 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2017-11-07 16:09:27 -0400
commitbc92cb5a599865efc79f38044c56cbf67143c2c7 (patch)
tree0ba0f3d9fb9349839659835e59d86774c09c2519
parentb31efa3aea2464089133d084d499f47d95cb0de7 (diff)
link to git ML post
-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)