From: John Levon <levon@movementarian.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>, smatch@vger.kernel.org
Subject: Re: Sync smatch with sparse?
Date: Thu, 29 Nov 2018 10:09:45 +0000 [thread overview]
Message-ID: <20181129100945.GA13841@movementarian.org> (raw)
In-Reply-To: <20181129100327.few3rq3tz7pe5ve5@ltop.local>
On Thu, Nov 29, 2018 at 11:03:28am +0100, Luc Van Oostenryck wrote:
> On Mon, Nov 26, 2018 at 10:49:09AM +0300, Dan Carpenter wrote:
> > It looks like everything was BCC instead of To: and Cc:? I can't tell
> > which went to linux-sparse and which smatch@vger.kernel.org. Smatch is
> > GPL and Sparse is MIT, but any shared code is MIT licensed.
> >
> > I would like to sync with upstream Sparse, but I tried a couple months
> > back and it got complicated so I have procrastinated.
>
> Hi Dan,
>
> It would indeed be good to sync smatch & sparse and I would be ready,
> if needed, to make some changes to sparse to make it easier.
> There is also several ways to do that. I'm wondering if you
> have already considered to simply remove anything related to
> sparse from smatch's tree and install sparse as a seperate library?
Right now I at least have changes in sparse that are very much
smatch-dependent, so this would be a real pain for me...
regards
john
next prev parent reply other threads:[~2018-11-29 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 12:08 [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason John Levon
2018-11-25 21:29 ` Luc Van Oostenryck
2018-11-25 23:29 ` John Levon
2018-11-26 0:27 ` Luc Van Oostenryck
2018-11-26 7:49 ` Dan Carpenter
2018-11-29 10:03 ` Sync smatch with sparse? Luc Van Oostenryck
2018-11-29 10:09 ` John Levon [this message]
2018-11-26 8:44 ` [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason John Levon
2018-11-26 9:18 ` Dan Carpenter
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=20181129100945.GA13841@movementarian.org \
--to=levon@movementarian.org \
--cc=dan.carpenter@oracle.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=smatch@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.