From: Christopher Li <sparse@chrisli.org>
To: Josh Triplett <josh@freedesktop.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
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, 2 Jul 2009 16:46:22 -0700 [thread overview]
Message-ID: <70318cbf0907021646y3b4a3ef7ieaaea51fa8d3bd51@mail.gmail.com> (raw)
In-Reply-To: <20090702232109.GJ19009@feather>
On Thu, Jul 2, 2009 at 4:21 PM, Josh Triplett<josh@freedesktop.org> wrote:
> Fortunately, Git offers a good solution to this problem: submodules.
> linux-2.6 could have Sparse as a submodule under the tools/sparse
> directory. Anyone who checked out linux-2.6 via git could then
> near-automatically get a copy of Sparse via git, and release tarballs of
> Linux could fairly easily include Sparse.
That sounds great. That is actually what I am looking for, clean history
and easy to use in kernel. I describe the similar idea without knowing the
git submodules. Now it can even sync nicely with the kernel.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-07-02 23:46 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
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 [this message]
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=70318cbf0907021646y3b4a3ef7ieaaea51fa8d3bd51@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=josh@freedesktop.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).