Actual behavior:
% git config --global lfs.fetchinclude 'external/linux/*64*'
% git submodule update --init
% [downloading packages matching 'external/linux/*64*']
% git config --global lfs.fetchinclude 'external/linux/*32*'
% git submodule update --init
[nothing happened]
Expected behavior
% git config --global lfs.fetchinclude 'external/linux/*64*'
% git submodule update --init
[downloading packages matching 'external/linux/*64*']
% git config --global lfs.fetchinclude 'external/linux/*32*'
% git submodule update --init
[downloading packages matching 'external/linux/*32]
Thanks for the report. I've marked it as a bug. My hunch is that since the submodule didn't change, git submodule update --init
doesn't do anything, bypassing the git smudge filter.
I think that:
$ git submodule update --init --force
# ...
should work as intended.
@ttaylorr, that actually also doesn't work, unfortunately.