From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 77D58C41514 for ; Mon, 5 Aug 2019 19:27:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4A02120C01 for ; Mon, 5 Aug 2019 19:27:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565033252; bh=MQ8FR72Dyq5oOL55TMoiwVjBxDH1WhMvPfmVW1mvDIQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=zczcQDmkwPCjvJMrf1X+4CUZ4gcCEhf2kLDzNb08DYprNQHXT6Y/PpO3oG6apoh/v rq2kEfo4p/4Lx6Mwbe5esDVvKQ5qfG00HUTkjUnnBWQ6eTLNVubrEf8LC0KbmLTpQD vuxpW1GaqUrD6+zrc5SIPsa9Bm2c+QfPn398TiZE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730483AbfHET1b (ORCPT ); Mon, 5 Aug 2019 15:27:31 -0400 Received: from mail-qt1-f178.google.com ([209.85.160.178]:43505 "EHLO mail-qt1-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727460AbfHET1b (ORCPT ); Mon, 5 Aug 2019 15:27:31 -0400 Received: by mail-qt1-f178.google.com with SMTP id w17so1489238qto.10 for ; Mon, 05 Aug 2019 12:27:30 -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:references:mime-version :content-disposition:in-reply-to:user-agent; bh=h1ewf34lHhC/ecib1hsGGIlixnNIzDn15kep7wiXFj4=; b=EverIdWBkbzrNKBtVjB/eEfEjEu95MHUnU5wBU8QlutwkoFjuV2QkwB4r0q4CLVmB/ QQlU8b6AEABq1mqziHyeOka6DTzr7MkEtLGiIKQLVfWMHVHBC7fTL6QM3upaV7R2qXi8 eV8XC4+v+h8mPIxGVQgYmEnGxAJ/12wtj0KV4= 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:references :mime-version:content-disposition:in-reply-to:user-agent; bh=h1ewf34lHhC/ecib1hsGGIlixnNIzDn15kep7wiXFj4=; b=rLTvlEIqYfE84ek/54z8dnxuEZnrPrCHCPBXPkkBXQO0fdGLVMcsiAdpb5pf8OcaHk 5GfWAEtUJ6y+kbrFj9ifQJofqreuajQLm2tQUZEuJ84hEp1LpoNweYUvpMIg+Z+Wxt6U ii203zF9UXFEtE0oPM/CtqmWFrwhite3lhSMvIHlgQ4OQFRnMMJGBaTQ8v10dhck+ogO k+kVmhZSoKq9YnciGuOErET8P4wvULUQUPMRc335e6qLCul/ZZSiuyJ3gVyCOIjgyFA0 mbIt8uq+04YABFN38Dk+hm6t4g81NSoM1iUjzzWKwDpgHFbks0NLVorLDH7rA2eIfTqr 8CTQ== X-Gm-Message-State: APjAAAVBwhDAxOYvpYC0VDrbfwzREJzDao9Iug6oyOVtsutDZa/GeROH x+fpF4n0It7G4KUbwD7WnY5vmQ== X-Google-Smtp-Source: APXvYqzNnb5aK5bFMZDX/1DWfTBCo+Ag0Lvk6m3WaIGVkXDEPpTNVColK/U4FuU9sJuchpQcA5KhYg== X-Received: by 2002:ac8:3f55:: with SMTP id w21mr108549934qtk.217.1565033249978; Mon, 05 Aug 2019 12:27:29 -0700 (PDT) Received: from chatter.i7.local (192-0-228-88.cpe.teksavvy.com. [192.0.228.88]) by smtp.gmail.com with ESMTPSA id j66sm35383650qkf.86.2019.08.05.12.27.29 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 05 Aug 2019 12:27:29 -0700 (PDT) Date: Mon, 5 Aug 2019 15:27:27 -0400 From: Konstantin Ryabitsev To: Linus Torvalds Cc: Micah Morton , linux-security-module , Linux Kernel Mailing List Subject: Re: [GIT PULL] SafeSetID MAINTAINERS file update for v5.3 Message-ID: <20190805192727.GA15470@chatter.i7.local> References: <20190805142756.GA4887@chatter.i7.local> <20190805191136.GB4887@chatter.i7.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 05, 2019 at 12:17:49PM -0700, Linus Torvalds wrote: >> However, I suspect that getting message-ids for all your pull >> requests >> would significantly complicate your workflow. > >Yeah, that would be a noticeable annoyance. If I were to process pull >requests the way I used to process emailed patches (ie "git am -s" on >a mailbox) that would be a natural thing to perhaps do, but it's not >at all how it ends up working. Having to save the pull request email >to then process it with some script would turn it into a chore. > >I think the pr-tracker-bot clearly catches most cases as it is, and >it's only the occasional "somebody did something odd" that then misses >an automated response. Not a huge deal. For me it was actually more >the "I didn't understand why the response didn't happen", not so much >"I really want to always see responses". Ok, let me add a fix for Re: at the start -- this won't make things significantly more expensive, but will catch this particular corner case. Best regards, -K