Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932817AbcK1LHf (ORCPT ); Mon, 28 Nov 2016 06:07:35 -0500 Received: from aserp1040.oracle.com ([141.146.126.69]:17503 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932523AbcK1LH1 (ORCPT ); Mon, 28 Nov 2016 06:07:27 -0500 Date: Mon, 28 Nov 2016 14:07:13 +0300 From: Dan Carpenter To: Mike Marshall Cc: Martin Brandenburg , Christophe JAILLET , LKML , kernel-janitors@vger.kernel.org Subject: Re: [PATCH] orangefs: Axe some dead code Message-ID: <20161128110713.GE28558@mwanda> References: <20161121221702.6438-1-christophe.jaillet@wanadoo.fr> <20161125215139.GM6266@mwanda> <20161126100229.GO6266@mwanda> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: userv0021.oracle.com [156.151.31.71] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1270 Lines: 33 On Sat, Nov 26, 2016 at 08:51:57AM -0500, Mike Marshall wrote: > I think I understand what you're saying, except for this part: > > > would have been secretly disapointed at your lack of > > courage in my heart but it would have been normal and fine. > What I'm saying is that for some people the cut off for 4.10 happens the week or two before 4.9 is released. I'm sending bugfixes and they still push them out to 4.11. It annoys me, secretly. > I'm pretty sure that Linus won't accept a pull request from me > at the wrong time and that I won't send one at the wrong time > on purpose. Linus pulls lots of things that make him unhappy. If he didn't compromise he would go mad. > > I've been laboring under the belief that the rc period is when > we "push only patches that do not include new functionalities", > and I would have thought that stripping out a few lines of dead > code would be appropriate then. > No. -rc is for fixing regressions only. If it's a fix for a bug that has *always* been there, then think carefully about how important it is because that's not a regression fix. If it's a bug fix, but it's not a regression fix and it's not critical then wait. Non-bugfixes should only go in during the merge window. regards, dan carpenter