Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1176218imm; Fri, 1 Jun 2018 17:29:35 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKrc3N57mYXhBt4cReMnaoSgURuX4isn2zSyKfairxVLxaI+kKexEyak0CTcbktKWxOKbdL X-Received: by 2002:a17:902:714e:: with SMTP id u14-v6mr6343139plm.289.1527899375544; Fri, 01 Jun 2018 17:29:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527899375; cv=none; d=google.com; s=arc-20160816; b=0ltW6ZjQQJ+LbHORjLSOTBR0Uvz8Z3it9m5/iCIKamwXJRQbd3wrA/J+mnyaAQYUui GdruxOLP5VgNg9OXqzoAzgLqFXe3N97ZxHaCZvyST96sxhNY0ndSLCCoDfmO+2dWIUro mCGPaaJRkEXPD2gfhBWRcNAIV/VP6bKro8r85cxPCdw5dgG0rm+3zmelgWXbK9RoELdS SJEfMQz8nDrB5BWTF63jPcee6p8SVxQSKUJp2k7OurZgbm3VI9G7bB3HhLISadFdsB0w 774hz1kK5f60v2KZG9HCR59nS+RcWFffaHCGsrvT1k+gwLZeBGD0iG2OfCVCuGdDFyWS nclQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:references :in-reply-to:subject:cc:date:to:from:arc-authentication-results; bh=sV8njANxhUeDYas/H4MTf7uIEYnDlpEuqhtmB7UPbGM=; b=ZC59ykEGMHjDEZEAniGfLJ1GATSZQFcAzSfZnbtEQPksAqkIGzNruW9pKDIEtVGO/d jbeUfbnfyOoXSIBpu6Jo49Ey/TYvhzuiaJJX25BrfszhlY4r5ngLPvXyFmNebZyzRazH DkT/2e9enZ7P8j3a9/djQoA5cpam9k+77CrdpeZGycrN3QzhyJuBiPm3nzPtBuKaqOgZ FFGP3NVvSpSWYdTggx3gw/Ih33o6b2yNT10qyzAn2Boe0rkcUMbjWrc13rkGqzA4GwaJ gunm7Foi9xdSGgP6CyF97AHMRDHtg52h8zVhoZo4vKbsbHfeEy2TmOfRJ5argEQPmh2w 8E7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g18-v6si22214214plo.533.2018.06.01.17.29.21; Fri, 01 Jun 2018 17:29:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751250AbeFBA2y (ORCPT + 99 others); Fri, 1 Jun 2018 20:28:54 -0400 Received: from mx2.suse.de ([195.135.220.15]:43648 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750758AbeFBA2v (ORCPT ); Fri, 1 Jun 2018 20:28:51 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 3E0B8AB08; Sat, 2 Jun 2018 00:28:50 +0000 (UTC) From: NeilBrown To: Greg Kroah-Hartman , Oleg Drokin , Andreas Dilger , James Simmons Date: Sat, 02 Jun 2018 10:28:38 +1000 Cc: linux-fsdevel@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov, lustre-devel@lists.lustre.org Subject: Re: [lustre-devel] [PATCH] staging: lustre: delete the filesystem from the tree. In-Reply-To: <20180601091133.GA27521@kroah.com> References: <20180601091133.GA27521@kroah.com> Message-ID: <87bmcurpzd.fsf@notabene.neil.brown.name> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Type: text/plain On Fri, Jun 01 2018, Greg Kroah-Hartman wrote: > > So, let's just delete the whole mess. Now the lustre developers can go > off and work in their out-of-tree codebase and not have to worry about > providing valid changelog entries and breaking their patches up into > logical pieces. I find it incredible that anyone would think that not having to "worry about providing valid changelogs" and not "breaking their patches up into logic pieces" could ever be seen as a good idea. I hope that if lustre development is excluded from mainline for a time, that we can still maintain the practices that demonstrably work so well. For the record: I'm not in favor of ejecting this code from mainline. I think that the long term result may be that it never comes back, and will like at least delay the process. But you must do what you think is best. Thanks, NeilBrown --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEG8Yp69OQ2HB7X0l6Oeye3VZigbkFAlsR5LcACgkQOeye3VZi gbmPsxAAvr7MWTuOxOV9FtPuu+c6OuCKo35Mg5WG3X4OpEUSqSitN8cmEB/2kAWX kPkXgWBeoczSOCLG+hJgUD87iDgGqAn6A/D3vDlHOmcKWAipu7DurZhPKEt6qC3S GjtNSejb98G/tAgeVnPAyTFXdQBx6KPCMeg+MfbNzzxQKCXfmUxNuASx1EmXQH6z zuDERm9jnF5jbTIox53D4in0i5GEUBbUOiD4K+MnDNhiyh02Kr8dCkUoKs1UJOJX H7sfaYJZumJuP9fL8GSqBk+AB1SJH/Box4o1JyI/u4XKHNxVw+BuT2ptWUA6vyBb Snja80L/LDH0Mm/AgWZYt+yR5NSc1onAU1LgfwnRj/UFVMFJvc2ZWBSBzvVGG7eB Uj2uBqCFYJ6az8wVWzWjhZfHlcemyTCR+nHIm+AwFXxmK5m5+hRbsJC9+sK3IWIv zl9gGrfLJK1FBAAGzMZ5hyyQkAlHFoSN2lo/HxknfT6SLrMsjWgR2KnyiajdXVEs rKF2/F8T4QeMaSMbWtpu2qtcV49v3/qpIC6L1ysWFHcLRhduFguunQjQOJdnJHHL WReoEYi9ianU5tXrfDzJNZZOW5z9DaWSgxJAQ/MDxw1dREDN468xsIXf9GrVvKMv nA4w+ADktG3het9Z6Hv3dHSq+Ffvi7ynuRW43r/Tj/BoGGk1N80= =zyLF -----END PGP SIGNATURE----- --=-=-=--