I just updated the submodules. Do a `git pull && git submodule update --recursive` from the outer luvit dir.
The reason doing a `git submodule update` didn't pull in the new commits is that only tells it to checkout the version specified in the submodule. If you want something newer, you have to enter the submodule and do a `git checkout master && git pull`. On Sun, Feb 15, 2015 at 11:46 AM, ibi sum <[email protected]> wrote: > > Sorry luvi-binaries > > > > Doesn’t seem to fix it, same error as before. I do “git submodule update” > and “git fetch”, but nothing comes down the wire .. > > > > ; > -- > Jay Vaughan > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "luvit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "luvit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
