From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122997 invoked by alias); 10 Feb 2019 14:45:36 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 122986 invoked by uid 89); 10 Feb 2019 14:45:35 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=2.1 required=5.0 tests=BAYES_00,BODY_8BITS,GARBLED_BODY,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=society, persons, arranged, understood X-HELO: mail.aegee.org Received: from mail.aegee.org (HELO mail.aegee.org) (144.76.142.78) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 10 Feb 2019 14:45:33 +0000 Authentication-Results: mail.aegee.org/x1AEj2IR022441; auth=pass (PLAIN) smtp.auth=didopalauzov DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1549809906; i=dkim+MSA-tls@aegee.org; r=y; bh=kC/Eu0VdUsLwb3XNQVQYRy9/agKAMJg9pn50sBgS6ic=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=MBspJMvbKlxBK/qjWXuoLpI+zWXZwynxbOkBcdwaZMaL8ZoA0nt3KBiEdVKdJcVAH CEr+ICIcL2Sr8MOOq9+Pk+wUbvX21cpKxISM1GoD2ga7JhWP8YYE7Akk/ioiOciv/P cNTedRAMufywfUB1DTRrSYnFOFHWfiUOTwV5eK6I2P/mofEzP8kHiLdEQZAkfYynVU 94ifcRXpfompCJQND5jGEc0HL1Nnk75dN6mZG5Qoy4HqrJYiQxwPyc7PEV28dZAhPR DHE3Frjv+KdyEA43LzDRWB/a60eHig6hEqZPHWtUTjr/1aMQ5Ovx8m3+zn92UTkZfO 3DN+TJ2uEzedCEOeG7uM+f9NfxovH2p9i56DYEV57eJw8a8w4eImfB7sytZ82NMA3S 0jpx+5J5c4voxPCDVOsYSt6vBh3oosjizfExRVltNv1yaDx1PvdeDJmQ4Lf4HcPUY3 A/d09fR0FZKmu7wq9FvyIBATmDejR+jbEwGaDOcBhbGALtdcG7fSisgXxZaksxwEvz Rc1LXYT8jC+8CH5aYH+esHbnn/6qDVaBjSyr/Bfij/bRa/oQDJy5rXaDogCRtp5kBg 3dQjCM0ub4H4XJECJcNXbwd0+151gyxAhE7qkOmWqFGjTqrbJ1fPtE6bZQKeJmmAuL veeNf3HrByr6dOUCW1/JriGk= Authentication-Results: mail.aegee.org/x1AEj2IR022441; dkim=none Received: from Tylan (dslb-088-066-133-073.088.066.pools.vodafone-ip.de [88.66.133.73]) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id x1AEj2IR022441 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Feb 2019 14:45:04 GMT Message-ID: Subject: Re: Make clear, when contributions will be ignored From: =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= To: Segher Boessenkool , Joseph Myers Cc: gcc-patches Date: Sun, 10 Feb 2019 14:45:00 -0000 In-Reply-To: <20190206124401.GO14180@gate.crashing.org> References: <25a0e5620b1e8a7a831ae9660c988f5dd98aa7dd.camel@aegee.org> <20181205171121.GQ3803@gate.crashing.org> <0990b8acd4cc08f74c1bf314851a113711dbfa04.camel@aegee.org> <20190206124401.GO14180@gate.crashing.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.31.91 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00679.txt.bz2 Hello, thanks to Serger and Joseph for the feedback. Acting primary upon reminders is a general phenomenon in the society, nothing specific to software teams. Think on public administration: it acts sometimes much more collaboratively, if a public/private/famous media reports on the workflows of the public administration. Public administration also reacts sometimes only, if reminders are sent. Not surprizing is, that talking with a public administration, about their policy on acting only after receiving a reminder, leads to nowhere, as making progress on this discussion with such an administration, needs a lot of reminders. In summary, such public administrations insist on their right to receive reminders before acting. Do you share the opinion, that whatever can be done after receiving a reminder, can be arranged also without reminder? If yes, how do you propose to proceed, so that a no-reminders-are-necessary-state is reached? I read in the answer of Segher, that the purpose of reminding is not only to ping, but also to filter the ones who are pernetrant and sending manually reminders is the means to verify, that the persons really want to make progress. It was certainly not intentionally meant this way, but this is a possible reading. Let me repeat, that the topic is not anyhow GCC specific, nor do I offend the society anyhow. To make things better, first the causes for the current state have to be understood. Raising the topic on GNU Tools Cauldron is a very good idea, but it likely approaches less people than on this mailing list, I am not that much inside the GCC processes and I do not know, whether I can visit the next meeting. Regards Дилян On Wed, 2019-02-06 at 06:44 -0600, Segher Boessenkool wrote: > On Fri, Dec 07, 2018 at 10:55:11AM +0000, Дилян Палаузов wrote: > > will it help, if Bugzilla is reprogrammed to send automatically weekly > > reminders on all patches, that are not integrated yet? > > No, that will not help. > > If an interested party sends a friendly ping, that is of course welcome. > But automated pings are spam: unwanted bulk mail. > > > The patch I proposed on 27th Oct was first submitted towards GDB and > > then I was told to send it to GCC. Here I was told to sent it to GDB. > > What shall happen to quit the loop? > > You can cc: both sides of the discussion. Either also gdb-patches, or also > whoever told you to send it to GCC instead, or both. And include a link to > the mailing list archive of your thread on gdb-patches in your mail to > gcc-patches, so that all parties can see the relevant context. Make it > easy for people to help you! > > > Segher