linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-sparse@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
Date: Thu, 18 Jun 2009 13:40:15 -0700	[thread overview]
Message-ID: <70318cbf0906181340j3b04b2b4hb95f6c8648dea70b@mail.gmail.com> (raw)
In-Reply-To: <20090618192058.GB14086@uranus.ravnborg.org>

On Thu, Jun 18, 2009 at 12:20 PM, Sam Ravnborg <sam@ravnborg.org> 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

  parent reply	other threads:[~2009-06-18 20:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 19:20 RFC: Move sparse.git inside linux-kernel-2.6.git? Sam Ravnborg
2009-06-18 19:34 ` Jeff Garzik
2009-06-18 19:57   ` Jeff Garzik
2009-06-18 20:13     ` Randy Dunlap
2009-06-18 20:18   ` Sam Ravnborg
2009-06-18 20:40 ` Christopher Li [this message]
2009-06-20 19:37   ` Samuel Bronson
2009-06-21 18:33     ` Christopher Li
2009-06-21 23:17       ` Samuel Bronson
2009-06-22  7:57         ` Christopher Li
2009-06-25 14:48         ` H. Peter Anvin
2009-07-02 23:21 ` Josh Triplett
2009-07-02 23:46   ` Christopher Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=70318cbf0906181340j3b04b2b4hb95f6c8648dea70b@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).