On Tue, Dec 23, 2008 at 01:57, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: >> >> BTW, I am normally lazy enough that I am happy about just submitting >> patches. On the other hand, I am tried of these sparse patches floating >> around the mailing list. I can start a branch to merge the proper patches. >> Maybe some thing like a development branch for sparse. >> Is that some thing other people want? > > Please do so. We need some progress on sparse and current maintainer > seems to be occupied by other things at the moment. > > Sam Hello. How about? http://git.zaytsev.su/git?p=sparse.git;a=shortlog;h=discuss This branch holds the two patch collections* I recently sent to the mailing list. I think it includes every useful patch that does not break the kernel check, and even some that do. ;) The last time we spoke (yesterday) Josh was going to merge the patches really soon. The idea was to merge everything except the context patches, make a release, add the context patches, and wait for someone to fix them. -- 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