From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Li Subject: Re: Upcoming sparse release RC5 Date: Wed, 9 Aug 2017 20:18:31 -0400 Message-ID: References: <20170808002331.f3g6l7yzhsq3vhxe@ltop.local> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-yw0-f174.google.com ([209.85.161.174]:36406 "EHLO mail-yw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752178AbdHJASc (ORCPT ); Wed, 9 Aug 2017 20:18:32 -0400 Received: by mail-yw0-f174.google.com with SMTP id u207so49665372ywc.3 for ; Wed, 09 Aug 2017 17:18:32 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Dibyendu Majumdar Cc: Luc Van Oostenryck , Linux-Sparse On Wed, Aug 9, 2017 at 5:10 AM, Dibyendu Majumdar wrote: > > I think that compile error should not be possible? Because before you > merge any patch presumably you build Sparse and run the tests? > > As for other changes that were later removed - in my view this is > valuable history as it tells people what was tried and discarded and > why. I still feel all history is good. > OK. I think my obsession of "clean up the history" is wrong and not worthy doing. Linus's criticism of sparse-next rebase is correct. I will just got back to the master doing the normal git pull and merges. That actually simplify my own work flow as we. Chris