Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp6146725imd; Wed, 31 Oct 2018 07:30:43 -0700 (PDT) X-Google-Smtp-Source: AJdET5dmM8xUvNdkMl/MhY3arUfdhyQBMYTvhbGBeh5hTupU9mA+DL4DlDhCuJ70XNKfm4uFKDVc X-Received: by 2002:a62:3101:: with SMTP id x1-v6mr1364425pfx.204.1540996243071; Wed, 31 Oct 2018 07:30:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540996243; cv=none; d=google.com; s=arc-20160816; b=EXV1RtJl4E5A1dkoObUi5qGgwSXniptLqTHZeOt+Tza9vMvuX4A7IPBGAH3/TNUTjt dMpPT+mAGjwfrSBqwCHRb6oEkDC5eNI1ST6TTfdWhsYq/iPX3Eo7djzlSwcL7r9G51Tm msS35ldVAHgiZhT+7VNxV7N16lJJgtjWd3peLcbJ/yixHTJ+KMdAqS5n8lSSshztiwmi to5VG2jmnVUr4dYUtdnFWIddECjEXRSIeQxj+YwOGQUg9sfbdTkvsT9bPKasbP+1m6Gn acsOxT1ppP/SdWrNjmUsd4Wegl9Z44OChH1kGRlqwa2+TinlBFwy9NrQU/xgRJMuCFAe iqkg== 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:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature; bh=S8M4uCfROE/MuCCdm1NVOeMId99rb3RiYbjAxks8pgI=; b=yS5SArXL47SXr4YubDCr4FIV76CZfjT9qDPHHgXtGoUhFlWhqNDtjkdoTrb/iNqgAa m52vxWkZdaNMo7OQ10e/Wwbm7Qyzx0EWXNCDl1UfbDbeGH0M81cEguFVB7ReVaQ7DuHH beicdCJy/+WJdLRR75FGDPJrfsgl0xAUkJ6hnM404Or9t1JWSoQXYV6/BcoWhVOle5Vy yYIoC4tEL69xgUTPuPQEcWhTlAX6S7hvvIPJU7nGTOiEJmgzjP13EvcqQUwabUEH/b9+ JJWjNiLZ4jboHXq5+9OtT6xSWQjFles5VxR1mySqjQExBP/wf9MbgS2VuSFmpAinudT+ U+SQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=google header.b=EDZ9C+pj; 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 33-v6si13250584plt.22.2018.10.31.07.30.26; Wed, 31 Oct 2018 07:30:43 -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=@linuxfoundation.org header.s=google header.b=EDZ9C+pj; 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 S1729582AbeJaX0V (ORCPT + 99 others); Wed, 31 Oct 2018 19:26:21 -0400 Received: from mail-ed1-f67.google.com ([209.85.208.67]:41255 "EHLO mail-ed1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729492AbeJaX0U (ORCPT ); Wed, 31 Oct 2018 19:26:20 -0400 Received: by mail-ed1-f67.google.com with SMTP id x31-v6so13780702edd.8 for ; Wed, 31 Oct 2018 07:28:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=S8M4uCfROE/MuCCdm1NVOeMId99rb3RiYbjAxks8pgI=; b=EDZ9C+pjmNi1/XIrovwYvGv7lKChfCUM5UG4YwpAWC+dDbJByVmAi+LH1GhgYLrLeU /+ObKcQV031/hcDdMi7XxfrLmcChjvXg6GzLSwzmCr5840EsczXgUMHi2XeLmIuddqUO n2o88bz6Bh2ndmfAdBp3+7eSCSXidNUTtSKMM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=S8M4uCfROE/MuCCdm1NVOeMId99rb3RiYbjAxks8pgI=; b=hloxJaSumZMRklr4mpU3A1Guf+twZXtLnz6Ku1QC3ZgxwFKjZsjdL7edLnHFzgZZ0L ksVDkFmqunKMapP+hMU2LvcVLpqYdXgfp5SjU7voACQ2RsREfbbEfPhAsDR3h8wTpZtf pf5ytGQnt/ZqBhvI5zAyJju3in9OGaZ8xNIkoJNba2TmW9aLfylTA4Lr360k7TIdrUZt U6MDBiZwz/lTth/5qhwRR0Iow1RN7Cu04oHArSr61JrifRbRxskZEQ7/pofLA5PnioGY nxPnutQNPAlbbgTP8TDkJR5cAg6qilDy0paKGky0LR0vFPR63guSZ4zddXs1BYMcrzxs 4nEQ== X-Gm-Message-State: AGRZ1gKaDujpNmn9b0pxcyHvgohVuoI6SOF9Y+Dsmm6wGz58eO2ChHtf hj/XHFwLLDgbKoP8OFZA7bkShQ== X-Received: by 2002:a50:b574:: with SMTP id z49-v6mr879226edd.219.1540996083031; Wed, 31 Oct 2018 07:28:03 -0700 (PDT) Received: from pure.paranoia.local (192-0-230-179.cpe.teksavvy.com. [192.0.230.179]) by smtp.gmail.com with ESMTPSA id m19-v6sm4780618ejz.70.2018.10.31.07.27.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 31 Oct 2018 07:28:01 -0700 (PDT) Date: Wed, 31 Oct 2018 10:27:56 -0400 From: Konstantin Ryabitsev To: Linus Torvalds Cc: kirill@shutemov.name, Linus Walleij , Boris Brezillon , Catalin Marinas , Christoph Hellwig , Guenter Roeck , Jacek Anaszewski , Jens Axboe , Mark Brown , Ulf Hansson , Greg KH , Linux Kernel Mailing List Subject: Re: Git pull ack emails.. Message-ID: <20181031142756.GA5679@pure.paranoia.local> Mail-Followup-To: Linus Torvalds , kirill@shutemov.name, Linus Walleij , Boris Brezillon , Catalin Marinas , Christoph Hellwig , Guenter Roeck , Jacek Anaszewski , Jens Axboe , Mark Brown , Ulf Hansson , Greg KH , Linux Kernel Mailing List References: <20181023093521.dm3l5oen2j7etsot@kshutemo-mobl1> <20181023200408.GA13179@chatter.qube.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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 Thu, Oct 25, 2018 at 07:13:59AM -0700, Linus Torvalds wrote: > It would be much nicer if the "notification" really did the right > thing, and created an actual email follow-up, with the correct To/Cc > and subject lines, but also the proper "References" line so that it > actually gets threaded properly too. > > That implies that it really should be integrated into the mailing list itself. > > But I don't know how flexible the whole lkml archive bot is for things > like this. But I assume you have _some_ hook into new messages coming > in for lore.kernel.org? > > > Would that be a useful alternative? If yes, what would be your preferred > > workflow for such tool instead of "git lmk [commit] [tree-moniker]"? > > I really do suspect that "I sent out a pull request, I'd like to be > automatically notified when it gets upstream" would be the primary > thing. > > And by "upstreamed" it isn't necessarily just my tree, of course. I should have something working soon, hopefully -- which should be sufficiently generic to be adapted for other devs. Regarding your case specifically, what's a good cutoff period for treating a pull request as effectively ignored/abandoned (i.e. no matching commit-id ever found in the repo). I'm guessing about a month, or do you want to go longer, in case something shifts to the following merge window? Regards, -K