On Thu, Jun 18, 2009 at 12:20 PM, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > > The linux kernel is one of the major customers of > sparse and several sparse hackers are very > active on the kernel front too. > > How about combining forces and move sparse.git inside > the kernel. I think it is better keep it separate. The main reason is to have a clean history. Sparse has much lighter activity than kernel. The sparse history will become noise compare to the kernel one. So it is not easy to bisect sparse bugs. It will sync tons of kernel source with it. That being said, I think we still can make sparse friendly to kernel. For example, we can make a sparse tree sym link under tools of the kernel tree. The kernel makefile will use that tree if it is there, as if it is part of the kernel. So we can have the benefit you mention without mess up the sparse history. We can even make some build target in the kernel to check out a copy of the sparse tree in the tools/sparse directory. That should solve the problem that people need to know where to check out. Chris -- 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
