Return-path: Received: from 1wt.eu ([62.212.114.60]:65182 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755948Ab2DNT7N (ORCPT ); Sat, 14 Apr 2012 15:59:13 -0400 Date: Sat, 14 Apr 2012 21:58:34 +0200 From: Willy Tarreau To: Felipe Contreras Cc: Stefan Richter , Adrian Chadd , Greg KH , Sergio Correia , linux-kernel@vger.kernel.org, stable@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk, linux-wireless Mailing List , Sujith Manoharan , "ath9k-devel@lists.ath9k.org" , "John W. Linville" Subject: Re: [ 00/78] 3.3.2-stable review Message-ID: <20120414195834.GI19802@1wt.eu> (sfid-20120414_220006_963044_6EFD6CD5) References: <20120413105746.10ffb120@stein> <20120413154216.476a02ac@stein> <20120414094137.54a7f213@stein> <20120414155733.GF19802@1wt.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sat, Apr 14, 2012 at 10:33:59PM +0300, Felipe Contreras wrote: > >> Again, what makes a released patch undroppable? > > > > Being applied, in other words, having a commit ID in the branch. > > Seriously? That's your reason? > > Hey, thousands of users out there; the reason why we pushed a patch > that is known to be broken in v3.3.x is because it already has a > commit ID. I think you have a real problem with logics in general as it's not the first time you're reverting cause and consequence in people's arguments. I'm basically saying that we don't revert patches any other way than by backporting the revert and you're saying that every patch has to be backported. Come on, this discussion makes no sense at all. You're wasting everyone's time for nothing, just because you want to be right even after everyone explained you the same thing. You got me bored. Willy