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 9AF445B1 for ; Thu, 29 Jun 2017 19:07:22 +0000 (UTC) Received: from mail-io0-f196.google.com (mail-io0-f196.google.com [209.85.223.196]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 57B4C18D for ; Thu, 29 Jun 2017 19:07:22 +0000 (UTC) Received: by mail-io0-f196.google.com with SMTP id 84so1759696iop.2 for ; Thu, 29 Jun 2017 12:07:22 -0700 (PDT) MIME-Version: 1.0 Sender: linus971@gmail.com In-Reply-To: <20170629182044.GP21846@wotan.suse.de> References: <1498754169.2834.61.camel@HansenPartnership.com> <1498758126.2834.70.camel@HansenPartnership.com> <20170629182044.GP21846@wotan.suse.de> From: Linus Torvalds Date: Thu, 29 Jun 2017 12:07:20 -0700 Message-ID: To: "Luis R. Rodriguez" Content-Type: text/plain; charset="UTF-8" Cc: James Bottomley , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Developing across multiple areas of the kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Jun 29, 2017 at 11:20 AM, Luis R. Rodriguez wrote: > > Linus has said before cross-tree collateral evolutions *could* just be sent to > him as a set of scripts he could run. It might sound easier said than done > though, but we can improve on the process by practicing it daily. I do take cross-tree stuff, and in particular don't mind things if they are obviously scripted cleanups (with the extreme case of that being to just send me the script - that makes it *really* obvious to me that it's scripted ;). That said, I generally end up considering it a last option. And that's not because I can't do it, but because things like that tend to be really painful for stable backporting etc. Cross-tree stuff has a tendency to also be large and invasive in other ways. If it's *small* and just cross-tree, that's fine, and I take it all the time, although because of general laziness I certainly prefer when it goes through somebody else (often the tip tree or Andrew Morton). In fact, the real problem with cross-tree things is often not that it affects multiple maintainers, but that it by definition doesn't have a maintainer AT ALL that tracks it and pushes it. So the "random occasional cross-tree updates" often end up languishing because nobody takes ownership of them. Linus