Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5517259yba; Wed, 8 May 2019 14:54:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqxY5YR6+/zrRIASCvxsW7X3bO6MMliRybCfCKpJVfuesIbRx38iMfR3//lcgS0/NIIxt3RX X-Received: by 2002:a63:e408:: with SMTP id a8mr672042pgi.146.1557352450216; Wed, 08 May 2019 14:54:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557352450; cv=none; d=google.com; s=arc-20160816; b=JwkixzxUvoKi9SBWm24yMQwOBQkwoIzngG7RLNnUY7rGEqiAc8Huoa2kBEZATEFlFe I2InD6CPNv+gfms3iJK3/11pD0VC8nfzUyNu0pmZZpBb/7uEOp+20vhbIhQcRGrWj+5j 3GbaYC68wMrrlr+Wd3pASdgOaX0X6lcdCea5QNc/XfLFz5uaCNbmOB5BrPImWSAl/Gpo 6Djqjb3t7FpFy+axNk0Jh4DkhaVuZz45O2GmkYVIbEcdC9v91mneWcJXvkhpzEkv6KaA KR79exDwef0gtZPJVYBlv4aJw3EjXwPtIJb3f15pjwG0l1ikI1M0BDnNHbtfYjLvLhxs 6ueA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=fxp7C3gn4hFeqHlulWo27PsHC7oweWrUUdBFO5/Emm4=; b=Tg/qL0FP/a6Lyv1qxuijPS5N7D4LaX6EYld4fIEY6X4c34MLlng8xeuTB3syd1wJbi j2NIHra1VU9k7S+GfWMQxrqts1QU+AKRZFnlktAc/Otkz8Z9TaC1Kjgw+SYEBoYZ04YA dPGb4sQZ0ivFOI4ww/4ExOGXcq4/Y/nEVI2KRy5ujklxjc/glJkIqecINrtpgHcXi4hd X7Tq5rwBLFbUX9jmaZ1wTEeE6HELIeY+QJcxGLTGjbq/1cDY5zFGfpc0viWInTTWei5K gRvuqIFR248Iw/jBGhl4B/R9ZY/kGZVTnrx1S6ZSD2wI7L2rqZTOhgfMVjQUzOFJQX1o fH5g== 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 r198si257347pgr.153.2019.05.08.14.53.54; Wed, 08 May 2019 14:54:10 -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 S1728550AbfEHVuw (ORCPT + 99 others); Wed, 8 May 2019 17:50:52 -0400 Received: from ms.lwn.net ([45.79.88.28]:55296 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726837AbfEHVuw (ORCPT ); Wed, 8 May 2019 17:50:52 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id E872E316; Wed, 8 May 2019 21:50:51 +0000 (UTC) Date: Wed, 8 May 2019 15:50:50 -0600 From: Jonathan Corbet To: Linus Torvalds Cc: Andreas Gruenbacher , cluster-devel , LKML , "Tobin C. Harding" , Dan Williams Subject: Re: GFS2: Pull Request Message-ID: <20190508155050.186a1ba4@lwn.net> In-Reply-To: References: <20190508145818.6a53dff5@lwn.net> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 8 May 2019 14:05:35 -0700 Linus Torvalds wrote: > On Wed, May 8, 2019 at 1:58 PM Jonathan Corbet wrote: > > > > I think this certainly belongs in the maintainer manual, but probably not > > in pull-requests.rst. There are a lot of things about repository > > management that seem to trip up even experienced maintainers; pre-pull > > merges is just one of those. I would love to see a proper guide on when > > and how to do merges in general. > > We had another pull request issue today, about a situation that I > definitely know you've written about in the past, because I linked to > lwn in my email: > > https://lore.kernel.org/lkml/CAHk-=wiKoePP_9CM0fn_Vv1bYom7iB5N=ULaLLz7yOST3K+k5g@mail.gmail.com/ Sigh, I never can escape my past sins... > and while I suspect people don't actually read documentation > (_particularly_ maintainers that have already been around for a long > time but still do this), maybe that part could be in the same > documentation? Something derived from that would make sense, yes. I'll see if I can't pull something together, unless by some delightful miracle somebody beats me to it. jon