[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180503114335.GY30522@ZenIV.linux.org.uk>
Date: Thu, 3 May 2018 12:43:35 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Sasha Levin <Alexander.Levin@...rosoft.com>,
"ksummit-discuss@...ts.linuxfoundation.org"
<ksummit-discuss@...ts.linuxfoundation.org>,
Greg KH <gregkh@...uxfoundation.org>, "w@....eu" <w@....eu>,
"julia.lawall@...6.fr" <julia.lawall@...6.fr>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: bug-introducing patches
On Wed, May 02, 2018 at 10:41:56PM +0200, Geert Uytterhoeven wrote:
> Between v4.17-rc1 and v4.17-rc3, there are 660 non-merge commits, of which
> - 245 carry a Fixes tag,
> - 196 carry a CC stable,
> - 395 contain the string "fix".
> (non-mutually exclusive)
BTW, what about situations when we have a fix naturally split into
a series of 2-3 massaging equivalent transformations + one-liner fix
in the resulting tree?
Powered by blists - more mailing lists