From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8E95FE47 for ; Fri, 7 Sep 2018 02:33:57 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 317467AF for ; Fri, 7 Sep 2018 02:33:57 +0000 (UTC) Date: Thu, 6 Sep 2018 22:33:54 -0400 From: Steven Rostedt To: Sasha Levin Message-ID: <20180906223354.7971fe50@vmware.local.home> In-Reply-To: <20180907014930.GE16300@sasha-vm> References: <20180904201620.GC16300@sasha-vm> <20180905101710.73137669@gandalf.local.home> <20180907004944.GD16300@sasha-vm> <20180907014930.GE16300@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug-introducing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 7 Sep 2018 01:49:31 +0000 Sasha Levin wrote: > Look at v4.17-rc8..v4.18: how many of those commits fix something > introduced in the v4.17 merge window vs fixing something older? I will note that from my own experience, I have found a lot of older bugs because new code that was added triggers the easier. Or I will find old bugs while debugging a bug that was introduced in the last merge window. Why should this bug that I found and fixed be treated differently than a bug that was introduced in the merge window. A lot of times, these older bugs become "crap, this is bad, I need to get this to stable ASAP" too. -- Steve