Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp3276351ima; Tue, 23 Oct 2018 03:22:01 -0700 (PDT) X-Google-Smtp-Source: ACcGV62CPfZq5CRRjq4gKUPH3cdZEKtUJ0chcvSz5hDZL6hS5ncLrlC71LiOiD2KGUPCn6c8I/cI X-Received: by 2002:a17:902:45a5:: with SMTP id n34-v6mr42214511pld.341.1540290121180; Tue, 23 Oct 2018 03:22:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540290121; cv=none; d=google.com; s=arc-20160816; b=1EmJRNDkD4BiqM4JbxmjuP7hdcxCeOEoQI3dKjlXC4jZ5jvQRLHcBGxYnMBPuT6f90 hTDoXNcKRanXtRof+CsI+jaKCv2Bv0UqTgrp4QhZl05Pqq3vRZt9jBGRmlDYXD2gtsHh 3reE77mBQbNynyWyE7mkzb+mWN7lhsR/5uBEjnP06SOtPkuYBqYy1HYQjwZnPAJIYCYI IDLkuzBJxl+6QqbPUQV351eoEW984+wehhciKPRlr4lzQCLZCXGOCnR17pA5pQrBqeVF OqOhusRDpvDbgxE4rpaAKEYjH46+vl4ED9OLp8tMl5joTuAlxDcfHMwB+vErfMzzeRN8 gYpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=HRL51koJrh5AVXAcZUx69Ja81tINm4qYzGot1c91YFE=; b=qTo+6qP1th87Jmj6c9ETz7DHTIZFUF0RZTNu2gcuODRB2X8qez8e1aw3So0z+2xZSV AAyoM2Ph0eRH4yZ/Z5tsxF68VCsH3EcWDVdQDzFdIjs2OtXqJYEQwiV7G3ODD2awPV58 7C1n04oKv9AMeoQWgG5TOluCNnsHqB1SedQPiGrYdgjlpfKL9N88l0mKQi7AK3QKoQry fodXtdlllZbROE9F6iQM7rTBS3mkifaJmghByCoFvVDPXazpKBHj30A3OQKD4dU57xfE nfIMwvwYT3rR9zpwOtyvsaCdQH/+opF1MI8G5in2jyMWHZ6KIWtA7G2AaaZ6rTql7SXD xETw== 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 w6-v6si910792pgm.557.2018.10.23.03.21.46; Tue, 23 Oct 2018 03:22:01 -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 S1728568AbeJWRqE (ORCPT + 99 others); Tue, 23 Oct 2018 13:46:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:37692 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727714AbeJWRqE (ORCPT ); Tue, 23 Oct 2018 13:46:04 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 3AD28AE67; Tue, 23 Oct 2018 09:23:30 +0000 (UTC) Date: Tue, 23 Oct 2018 11:23:29 +0200 Message-ID: From: Takashi Iwai To: Linus Torvalds Cc: Boris Brezillon , Catalin Marinas , Christoph Hellwig , Guenter Roeck , Jacek Anaszewski , Jens Axboe , Linus Walleij , Mark Brown , Ulf Hansson , Greg KH , Linux Kernel Mailing List , Willy Tarreau Subject: Re: Git pull ack emails.. In-Reply-To: <20181023090245.GC23341@1wt.eu> References: <20181023090245.GC23341@1wt.eu> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/26 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 23 Oct 2018 11:02:45 +0200, Willy Tarreau wrote: > > On Tue, Oct 23, 2018 at 09:41:32AM +0100, Linus Torvalds wrote: > > Because yes, the second option likely works fine in most cases, but my > > pull might not actually be final *if* something goes bad (where bad > > might be just "oops, my tests showed a semantic conflict, I'll need to > > fix up my merge" to "I'm going to have to look more closely at that > > warning" to "uhhuh, I'm going to just undo the pull entirely because > > it ended up being broken"). > > Is that a big problem ? I mean probably those who need an ACK just want > to be sure their PR was not lost between them and you. It's not a guarantee > that the code will be kept till the release anyway, and I tend to think > that changing your mind after attempting a build is not different than > changing your mind 3 days later. So when this happens, you're possibly > expected to simply notify the author later saying "sorry, I changed my > mind and finally I dropped your code for this or that reason". That > should be enough to cover the vast majority of use cases, no ? Agreed, the ACK mail doesn't necessarily mean that everything right, but just ACK that the pull request is being processed. The e-mail communication can go wrong pretty easily (happened once or twice for my past PR's), so a simple ACK would relieve me wrt that point -- as Greg's ACK did indeed. thanks, Takashi