Skip to contentSkip to conversation

Development version of sparse?

DISCUSSION Eric Biggers 2 participants 2 messages Oct 11, 2016 Sparse checker

lore
Share & tools
lore
#0 lore raw

Hi,

I found that the "official" sparse repository,
git://git.kernel.org/pub/scm/devel/sparse/sparse.git, only contains patches up to January 2015.

There is another repository, which was more difficult to find, which contains some more recent patches, but only up to January 2016:
http://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git

There have been a number of useful patches posted to the mailing list since then which don't appear in either repository, such as fixing the prototype for __builtin_object_size().

Which one, if either, is currently the "official" repository for sparse? Is Chris L. still the maintainer?

And if the official repository has changed, can we get some of the links updated? For example the one on
https://sparse.wiki.kernel.org/index.php/Main_Page.

Thanks,

Eric

#1 lore raw
Quoted 17 lines · Eric Biggers

Hi,

I found that the "official" sparse repository,
git://git.kernel.org/pub/scm/devel/sparse/sparse.git, only contains patches up to January 2015.

There is another repository, which was more difficult to find, which contains some more recent patches, but only up to January 2016:
http://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git

There have been a number of useful patches posted to the mailing list since then which don't appear in either repository, such as fixing the prototype for __builtin_object_size().

Which one, if either, is currently the "official" repository for sparse? Is Chris L. still the maintainer?

Quoted 8 lines

And if the official repository has changed, can we get some of the links updated? For example the one on
https://sparse.wiki.kernel.org/index.php/Main_Page.

Thanks,

Eric
--

Hi,

Yes, the official repository is indeed:
git://git.kernel.org/pub/scm/devel/sparse/sparse.git

I consider the other one as Chris' staging/pending tree and indeed it contains some commits which have never been pushed to the official tree. And since August 2015, there have been a now a bunch of patches posted on the mailing list which haven't received any actions or comments from the maintainer.

Yes, Chris Li is still the maintainer.

Luc Van Oostenryck