From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753182AbbJWLxM (ORCPT ); Fri, 23 Oct 2015 07:53:12 -0400 Received: from imap.thunk.org ([74.207.234.97]:40031 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751959AbbJWLxI (ORCPT ); Fri, 23 Oct 2015 07:53:08 -0400 Date: Fri, 23 Oct 2015 07:52:08 -0400 From: "Theodore Ts'o" To: Peter Zijlstra Cc: Chris Metcalf , Gilad Ben Yossef , Steven Rostedt , Ingo Molnar , Andrew Morton , Rik van Riel , Tejun Heo , Frederic Weisbecker , Thomas Gleixner , "Paul E. McKenney" , Christoph Lameter , Viresh Kumar , Catalin Marinas , Will Deacon , Andy Lutomirski , linux-doc@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Message-ID: <20151023115208.GC7917@thunk.org> Mail-Followup-To: Theodore Ts'o , Peter Zijlstra , Chris Metcalf , Gilad Ben Yossef , Steven Rostedt , Ingo Molnar , Andrew Morton , Rik van Riel , Tejun Heo , Frederic Weisbecker , Thomas Gleixner , "Paul E. McKenney" , Christoph Lameter , Viresh Kumar , Catalin Marinas , Will Deacon , Andy Lutomirski , linux-doc@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org References: <1443453446-7827-1-git-send-email-cmetcalf@ezchip.com> <1445373372-6567-1-git-send-email-cmetcalf@ezchip.com> <20151021123900.GD3604@twins.programming.kicks-ass.net> <562947B0.7050103@ezchip.com> <20151023090459.GW17308@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151023090459.GW17308@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 23, 2015 at 11:04:59AM +0200, Peter Zijlstra wrote: > > If you think this is actually the wrong thing, is it worth trying > > to fix the git docs to deprecate this option? > > As said in the other email; git has different standards than lkml. By > now we're just one of many many users of git. Even git developers will create a new thread for a large (more than 2-3 patches) patch set. However, for a single patch, people have chained the -v3 version of the draft --- not to the v2 version, though, but to the review of the patch. And I've seen that behavior on some LKML lists, and I'm certainly fine with it on linux-ext4. But if you have a huge patch series, and you keep chaining it unto the 8th, 10th, 22nd version, it certainly will get **very** annoying for some MUA's. The bottom line is that you should use common sense, and it can be hard to document every last bit of what should be "common sense" into a rule that is followed by robots or a perl script. (Which is one of the reasons why I'm not fond of the philosophy that every single last checkpatch warning or error should result in a "cleanup" patch, but that's another issue.) Cheers, - Ted