From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from movementarian.org ([178.79.150.28]:36304 "EHLO movementarian.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726621AbeK2VOf (ORCPT ); Thu, 29 Nov 2018 16:14:35 -0500 Date: Thu, 29 Nov 2018 10:09:45 +0000 From: John Levon Subject: Re: Sync smatch with sparse? Message-ID: <20181129100945.GA13841@movementarian.org> References: <20181125212955.6kz3tsf735yrekug@ltop.local> <20181125232914.GA29607@movementarian.org> <20181126002734.rmk5kmvtjtol2m2h@ltop.local> <20181126074909.GI2970@unbuntlaptop> <20181129100327.few3rq3tz7pe5ve5@ltop.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181129100327.few3rq3tz7pe5ve5@ltop.local> Sender: smatch-owner@vger.kernel.org List-ID: To: Luc Van Oostenryck Cc: Dan Carpenter , smatch@vger.kernel.org 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