Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp3230161ima; Tue, 23 Oct 2018 02:30:03 -0700 (PDT) X-Google-Smtp-Source: AJdET5efonM4C+1gTL21WQ2mCUqxMDWthILVM+gOjKm9LcpXLIwRptW26wjqcoEpiVUGvP3FnAzM X-Received: by 2002:a17:902:748a:: with SMTP id h10-v6mr10350562pll.187.1540287003397; Tue, 23 Oct 2018 02:30:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540287003; cv=none; d=google.com; s=arc-20160816; b=LISlV5csMrZiQ1VKGxY0QzjwShMZfAP8OxgSSuYumahnw19i9uLw5shK8GpCO1xM7N TXl3S3wltDJxInQI3EakT6QTKsaeh75YzVK+3dfNa12GZPpVCDM1oNhOpVn2JMivZQEa XYLflqm4xSl54xd1wS0arcpMcrpihcMWLbWKNYNJFibtJSeoZ3AnXPkTHyRFT98qiZCe pGI65jRqL4KhOcItgtt465MDoZMyb/csaWVu4c7RbA46e3Kl7QLXjT1befFQtQuV8xT0 zd+UTgBdESZ62+f8H1FIS8AZvF0Se3WsHs8yU41Jh/TH8rl65pOlfhpAOGGOQCI0FLA1 LZcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=zyx9ITxuk19t8+QRaZ8ympInPihH0rce6mgHLtnoCcg=; b=ze3BPssr0Qzdz9R4X9pLODrtSea7LHu5wq+fmjqdPT0F046KVGPh6ll34oWhR+MHgq 053BIR/Fx6DR6J692vdw9nb45ykFjjfwB1+O13Vy16Cqs+deDELlghFeeQydABkS44JS fDRJCN7YSRVejqiifNnm2WsSV/5qg+hx8f8avUFY4TJ58hXORPQOh5PrB3RLpWCziquD o2K2oQtFl09J8lHg8GL3sgJiiU2dDyCtUBLYCAQRa8hWxb9ZcxmHnlV0/pZEXjm0Un49 X7JyUq+y8Mso29/tU404vtCKrAvA+xXoNDIV/E/Ywc7qMzv97lqkJ2eAP3+wqRXVIyX0 9tKA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=NIDZfecR; 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 e62-v6si752330pfe.31.2018.10.23.02.29.46; Tue, 23 Oct 2018 02:30:03 -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; dkim=pass header.i=@kernel.org header.s=default header.b=NIDZfecR; 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 S1728593AbeJWRud (ORCPT + 99 others); Tue, 23 Oct 2018 13:50:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:43694 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727714AbeJWRud (ORCPT ); Tue, 23 Oct 2018 13:50:33 -0400 Received: from localhost (unknown [185.7.230.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4D25F20665; Tue, 23 Oct 2018 09:27:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1540286879; bh=mVvJJ40S1Zy1t/hAkNla28BVCNIUzsKVVXifDxZVJGk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NIDZfecRnG/16SPs7TtJ5gTcz1X0RJTFDZIbQeJIte5dXVRSIDxQ3P0e4vxlcf+5K sXNkilaWIorBHGRfpFy19Ws7n2qiCZK6l2a3ApR5iLk4MYs5LISlyV5/FpHmS8phJ+ WDTb8JHUWoKpfaSFdc4AeZEMa+V9DtWgcyFY+dqQ= Date: Tue, 23 Oct 2018 10:25:34 +0100 From: Greg KH To: Linus Torvalds Cc: Boris Brezillon , Catalin Marinas , Christoph Hellwig , Guenter Roeck , Jacek Anaszewski , Jens Axboe , Linus Walleij , Mark Brown , Ulf Hansson , Linux Kernel Mailing List Subject: Re: Git pull ack emails.. Message-ID: <20181023092534.GB4659@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 23, 2018 at 09:41:32AM +0100, Linus Torvalds wrote: > In particular, the issue is that after each pull, I do a build test > before the pull is really "final", and while that build test is > ongoing (which takes anything from a few minutes to over an hour when > I'm on the road and using my laptop), I go on and look at the *next* > pull (or one of the other pending ones). > > So by the time the build test has finished, the original pull request > is already long gone - archived and done - and I have moved on. > > End result: answering the pull request is somewhat inconvenient to my > flow, which is why I haven't done it. I had this same issue, as I had full builds run and had to wait for the results. But I had a much smaller number of pull requests, so I just dumped them all into one folder and then did the responses when the tests came back. So I had the same issue as you, but you have much more requests to deal with, sorry. greg k-h