On Thursday, November 3, 2016 at 4:06:53 AM UTC-4, Magnus Therning wrote: > I notice you don't have a .gitmodules file in the folder in > question. So, maybe you'll find the reason for the oddity if you first > locate the .gitmodules file that produces that error? >
It seems there is some issues <https://github.com/VundleVim/Vundle.vim/issues/226#issuecomment-13779066> about submodules in Vundle [my emphasis]: > jdevera <https://github.com/jdevera> commented on Feb 19, 2013 > <https://github.com/VundleVim/Vundle.vim/issues/226#issuecomment-13779066>*I > still believe it makes no sense to use vundle and submodules at the same > time. Vundle is all about keeping everything up to date, submodules are all > about locking into a specific version. Actually, once of the planned > features to add to vundle is to lock certain plugins in a specific branch > or tag or commit, which would then make submodules even more useless. With > submodules, you are doing the work, without submodules, vundle does it for > you. * What's more, the problem resolved itself. I did a system update (in Archlinux) and git was updated (2.10.1-1 -> 2.10.2-1) and Vim (8.0.0046-2 -> 8.0.0055-1) And I still don't have submodules in any of my Vundle bundles! Magnus, Do your Vundle bundles have these files? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
