From 98fb47723990ce5af2eea7a52e4dd09add54ab99 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 1 Mar 2016 16:34:41 -0400 Subject: followup --- .../comment_1_fb01d4b5af500affc08a5c3b3b1849dd._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/git-annex_confuses_Git_with_nested_submodules/comment_1_fb01d4b5af500affc08a5c3b3b1849dd._comment (limited to 'doc') diff --git a/doc/bugs/git-annex_confuses_Git_with_nested_submodules/comment_1_fb01d4b5af500affc08a5c3b3b1849dd._comment b/doc/bugs/git-annex_confuses_Git_with_nested_submodules/comment_1_fb01d4b5af500affc08a5c3b3b1849dd._comment new file mode 100644 index 000000000..41068b5a9 --- /dev/null +++ b/doc/bugs/git-annex_confuses_Git_with_nested_submodules/comment_1_fb01d4b5af500affc08a5c3b3b1849dd._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-03-01T20:25:13Z" + content=""" +Reproduced this. + +This really does feel like a git bug. git is supposed to treat "gitlink" +files and .git symlinks the same. While modern versions of git set up +gitlink files for submodules, older versions of git used .git symlinks, and +git should still support that. + +Looks like the problem can be worked around, by setting +`GIT_DIR`. In your example, `GIT_DIR=../.git/modules/sub_lvl1/ git +submodule add /src/somegitrepo sub_lvl2` +"""]] -- cgit v1.2.3