From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115135 invoked by alias); 23 Nov 2019 07:17:06 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 115125 invoked by uid 89); 23 Nov 2019 07:17:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=importance, academic X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 23 Nov 2019 07:17:04 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:55948) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iYPfB-0005II-Qs; Sat, 23 Nov 2019 02:17:01 -0500 Received: from [176.228.60.248] (port=2105 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iYPfB-0002iU-6V; Sat, 23 Nov 2019 02:17:01 -0500 Date: Sat, 23 Nov 2019 07:17:00 -0000 Message-Id: <83imnbuknp.fsf@gnu.org> From: Eli Zaretskii To: Simon Marchi CC: joseph@codesourcery.com, gdb-patches@sourceware.org In-reply-to: <545dd677-52a2-5e04-536d-5af4d6850b83@simark.ca> (message from Simon Marchi on Fri, 22 Nov 2019 17:03:54 -0500) Subject: Re: Multiple identical mails from Gerrit References: <83wobrvhv2.fsf@gnu.org> <1db7ebdb-e98b-ba9b-2ac5-e454a1832578@simark.ca> <83lfs7vcvu.fsf@gnu.org> <545dd677-52a2-5e04-536d-5af4d6850b83@simark.ca> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00784.txt.bz2 > Cc: gdb-patches@sourceware.org > From: Simon Marchi > Date: Fri, 22 Nov 2019 17:03:54 -0500 > > >> Why do these trigger sending email at all? We didn't get email about > >> pushing changesets before Gerrit, so why do we need them now? > > > > On the glibc side, I tend to agree with that - people wanting to see what > > was pushed to master can follow glibc-cvs. > > I think that having a notification saying that the patch was pushed is nice. People > reply "I pushed the patch", so we might as well let the system do it automatically > anyway. My problem with these messages is that I have to look at the fine details of the Subject line, and perhaps also at the beginning of the body, to understand whether I need to review the patch. Since I only review the documentation parts, and rarely look at other parts of the changeset, it is important for me to be able to quickly understand whether a posted patch needs my attention. And these messages, which look almost exactly like an RFA but for minor details, make this harder. But maybe I'm the only one who is in this situation, in which case I'll have to live with this. > I could maybe get rid of the second one (state change), I'll have to look in the configuration. Thanks you. > Anyway: https://sourceware.org/ml/gdb-patches/2019-11/msg00749.html Yep. So maybe this issue is of academic importance ;-)