From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cross.elm.relay.mailchannels.net (cross.elm.relay.mailchannels.net [23.83.212.46]) by sourceware.org (Postfix) with ESMTPS id 97AE1388A421 for ; Tue, 9 Mar 2021 18:28:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 97AE1388A421 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=gotplt.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=siddhesh@gotplt.org X-Sender-Id: dreamhost|x-authsender|siddhesh@gotplt.org Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3BB7D102347 for ; Tue, 9 Mar 2021 18:28:46 +0000 (UTC) Received: from pdx1-sub0-mail-a30.g.dreamhost.com (100-96-15-19.trex.outbound.svc.cluster.local [100.96.15.19]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id D3EE4101E34 for ; Tue, 9 Mar 2021 18:28:45 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|siddhesh@gotplt.org Received: from pdx1-sub0-mail-a30.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.15.19 (trex/6.0.2); Tue, 09 Mar 2021 18:28:46 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|siddhesh@gotplt.org X-MailChannels-Auth-Id: dreamhost X-Print-Invention: 44b57e0d43e70206_1615314526082_2931470306 X-MC-Loop-Signature: 1615314526082:537218446 X-MC-Ingress-Time: 1615314526081 Received: from pdx1-sub0-mail-a30.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a30.g.dreamhost.com (Postfix) with ESMTP id 30DAA7E694 for ; Tue, 9 Mar 2021 10:28:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gotplt.org; h=from:subject :to:message-id:date:mime-version:content-type :content-transfer-encoding; s=gotplt.org; bh=Z1wFmrX33/exBb+xlan eo5h5u/8=; b=RXglai5oe+w0n1J74hyPfxd7NbDs4siyb4YqYeEIxJ+oOHL0Y7c ZySaI/gdDJiOJMtQuy7E+OlYp3zKkdHNnc5QPkmrKg1CqN3TGwGZt6XBr2AC/8I2 WD2CvqtiGY6bWjWIX0aTkp9fh+bJN/9O76DzPwlLdPkCcStzWHFHg5lc= Received: from [192.168.1.111] (unknown [1.186.101.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: siddhesh@gotplt.org) by pdx1-sub0-mail-a30.g.dreamhost.com (Postfix) with ESMTPSA id 537227E6B7 for ; Tue, 9 Mar 2021 10:28:43 -0800 (PST) X-DH-BACKEND: pdx1-sub0-mail-a30 From: Siddhesh Poyarekar Subject: [RFC] Auto-posting committed patches to this list? To: libc-alpha@sourceware.org Message-ID: <0d14c1fb-6f72-9b48-cea5-4a40c1da5635@gotplt.org> Date: Tue, 9 Mar 2021 23:58:39 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3030.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2021 18:28:49 -0000 Hi, There are quite a few patches that get pushed to git with minor modifications; it's a convenient workflow hack since it allows committers to push trivial changes when they don't really need additional review. That however breaks patchwork patch detection since the checksums against the diffs don't match. There are bugs in patchwork (or to see it another way, bugs in email clients) that prevent this too, but trivial changes are a pretty big percentage. I have a wrapper script that, whenever it updates my repo, checks for the patchwork patch for each commit and updates its state. I currently do it on need basis, but I could make it a cron job. How annoying would it be for folks here if the script, upon not finding a suitable patch, email it to the list as [committed]? As a bargain chip, one would no longer have to send an email whenever they push trivial changes to the repo; my sync would do it for them. This is not just to make the patchwork backlog cleaner, but also to make sure that the community is aware of the final version of the patch that went in; they're easier to correlate in the same list since they'd typically have the same subject line. This should eventually become a post-receive hook in the upstream repo, but I want to see if this workflow actually works for us before proposing this deeper change. Thoughts? Siddhesh