From c05570bd990ff5a0e8cf8a56f53ac521b3a5461a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 7 Nov 2017 16:09:27 -0400 Subject: [PATCH] link to git ML post --- .../comment_5_cb5332119c54764b4ef1e000b3767b0e._comment | 1 + 1 file changed, 1 insertion(+) 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 f6c6e5f4f0..5cc9dc6787 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. + git-annex could avoid the problem by not using relative paths of course, but there are reasons including shorter path length (generally)