On Fri, Jul 06, 2018 at 05:38:33PM +0000, Bart Van Assche wrote: > > Hello Luc, > > Thanks, I had missed Miroslav's patch. BTW, which sparse repository do you > recommend that I pull from to obtain a recent and stable version of sparse? The > git://git.kernel.org/pub/scm/devel/sparse/sparse.git repository mentioned on > https://sparse.wiki.kernel.org/index.php/Main_Page, https://github.com/lucvoo/sparse > or https://github.com/lucvoo/sparse-dev? > > Thanks, The tree at: https://github.com/lucvoo/sparse-dev is my own development/work-in-progrees tree. It mainly contains my WIP topic branches. These branches are not stable and are rebased. I mainly use this tree to share patch series for testing & review. The official tree is the one on kernel.org: git://git.kernel.org/pub/scm/devel/sparse/sparse.git and is stable and relatively recent but: 1) it lacks some essential patches to avoid tons of useless noises, like for example the patch: https://patchwork.kernel.org/patch/10334355/ 2) it lacks numerous fixes and improvements, like these overflow builtins, but many others too. 3) Christopher, the maintainer, is AWOL since a few months. He even never sent an announcement for the last release. So, I collect patches from myself and from others in the tree: git://github.com/lucvoo/sparse.git https://github.com/lucvoo/sparse This tree is stable, very well tested, never rebased and contains numerous fixes and improvements. Of course, ideally, my stable tree should be merged into the official tree, like Linus already asked Chris to do (twice). But for now, I strongly suggest to use my stable & up-to-date tree on github: git://github.com/lucvoo/sparse.git Sorry if the situation is a bit confusing. I'm far from being satisfied with it myself. -- Luc Van Oostenryck -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
