On Wed, Oct 3, 2018 at 8:27 PM Finn Thain <fth...@telegraphics.com.au> wrote: > > On Wed, 3 Oct 2018, Leonardo Bras wrote: > > > > > Sorry, I was not very clear at my reasons why this change is important, > > I will try to briefly explain the whole story. > > > > Some weeks ago I was trying to solve a task that needed to change some > > compiling options, build the whole kernel (allyesconfig) and look for > > errors. The problem was: It would take a long time to build everything > > in my computer. And many friends with slimmer laptops would take much > > longer. > > > > It seems to me that you shouldn't need expensive optimization for > continuous integration. In theory that could make a big difference though > I admit to no experience of build farms. > > Have you looked at ccache? It will save you from having to recompile any > files not changed. > > You could also leverage all of your laptops together using distcc. > > HTH. > > --
Both ccache and distcc seem very interesting, I will take my time to study them better as they can solve some situations I face. Thanks for sharing! Still, I believe my patchset is relevant, as it would enable people to rebuild the whole kernel (with build flags changes, for example) at the cost of only git-pushing the changes to a fork of my Gitlab repo, and waiting 3 hours. Thanks for helping!
