summaryrefslogtreecommitdiff
path: root/fsmonitor.c
diff options
context:
space:
mode:
authorLibravatar Jonathan Tan <jonathantanmy@google.com>2021-09-09 11:47:27 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-09-09 14:09:30 -0700
commit5df5106e1e8b52ff54c0726ba6919afa4b745980 (patch)
tree41e0ead2b0d6e5ec2dde1695ff2afe28c8739a1e /fsmonitor.c
parentt7814: show lack of alternate ODB-adding (diff)
downloadtgif-5df5106e1e8b52ff54c0726ba6919afa4b745980.tar.xz
submodule: remove unnecessary unabsorbed fallback
In get_submodule_repo_for(), there is a fallback code path for the case in which a submodule has an unabsorbed gitdir. (See the documentation for "git submodule absorbgitdirs" for more information about absorbed and unabsorbed gitdirs.) However, this code path is unnecessary, because such submodules are already handled: when the fetch_task is created in fetch_task_create(), it will create its own struct submodule with a path and name, and repo_submodule_init() can handle such a struct. This fallback was introduced in 26f80ccfc1 ("submodule: migrate get_next_submodule to use repository structs", 2018-12-05). It was unnecessary even then, but perhaps it escaped notice because its parent commit d5498e0871 ("repository: repo_submodule_init to take a submodule struct", 2018-12-05) was the one that taught repo_submodule_init() to handle such created structs. Before, it took a path and always checked .gitmodules, so it truly would have failed if there were no entry in .gitmodules. (Note to reviewers: in 26f80ccfc1, the "own struct submodule" I mentioned is in get_next_submodule(), not fetch_task_create().) Signed-off-by: Jonathan Tan <jonathantanmy@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'fsmonitor.c')
0 files changed, 0 insertions, 0 deletions