> Wow, I didn't think anyone was following that close on rPi. The reason it > broke was because we pushed a new feature to luvit that required a new > version of luvi-binaries. I didn't wait till the rPi build had finished > since it takes so much longer. >
Well I’ll be testing with rPi as my prime platform from here on out, so I’ll keep an eye out on broken things. The rPi provides a perfect test platform for my luvit needs .. > Now that I know someone follows closely on raspi, I'll wait for all builds > before pushing changes to luvit. > Okay, cool. FWIW, I tend to always run “make test” after getting new updates, so if it breaks early I’ll notice it. > Btw, the build finished a while ago, you can manually update luvi-builds in > the lit submodule. Sorry I’m not seeing luvi-builds .. can you explain this a bit further? ; -- 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
