From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 35321 invoked by alias); 11 Feb 2019 12:44:51 -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 35272 invoked by uid 89); 11 Feb 2019 12:44:50 -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,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=HAuthentication-Results:auth, persons, arranged, aforementioned 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; Mon, 11 Feb 2019 12:44:46 +0000 Authentication-Results: mail.aegee.org/x1BCiVPw004767; auth=pass (PLAIN) smtp.auth=didopalauzov DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1549889073; i=dkim+MSA-tls@aegee.org; r=y; bh=RhkcsNhOI4XWqu96S1OOBfcKgsE9XrsG6RSXwmVo+pw=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=Lh2Hl5YtSAzKFJiVtpNKYdXjvDhcvlr++vvT1NNjVCB/Om28pHBZ2Gx3DnsuvY7JB ywL0NrnHnk+hrOqI8lo5MplS2KFjWCq8j+CkPIPsM+SPHMHdrjRBStojlnqkXMi/50 9+M/YgrowyB22+SjMzmgGELQUsKYF43KTdRmMUT6PARwE0cNEggnGtWBwOR5nh4Xcu wqnokEKkRcb16hwUn040tx+X5wxhpjp/g5WtDdqeVDZeuJkua2xqr2XbzbZ8paQO0A MjIAHoi3d9eMB1l76RomNlshrbcLrhrt/SXDdwRO65jlaVVeEF5R2lUJmSvmhoREqS VaQbcu0FEagKwKw8c1bJ7shxAu3rXx8I1+iISZkzNXVXCuPsqGAXJY3lJsneU01ldU A1b3v6Ux1/fNED/mIQiuyOVnJ2cc0lNAcgEzHr61f3yC90ZZb4FEpg7kKKeMLbW+4K QM2NvYm4mGTOypz9lCKlGoglmxc95nyNTwlPCmFLw9dkX7gQecyBQPwLSKAXGMUjhq rX+O/os3r4n61Kn6yB7thZQzK+Wv4p+UMVKfcWcriQXyGAIs39VKIWLfbRTNiE2Vpl xaVKaan0KOMIi7+KLyXqDjpAPQ9bHXgleERcytjtsHvd4jDaT9eNf4GTggrNJREs/W VDPXiH5uu1GwFI/UPrnj3FLU= Authentication-Results: mail.aegee.org/x1BCiVPw004767; 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 x1BCiVPw004767 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 11 Feb 2019 12:44:32 GMT Message-ID: <120af439a98fc4160e684fca11fc63715e20ca93.camel@aegee.org> 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 Cc: Joseph Myers , gcc-patches Date: Mon, 11 Feb 2019 12:44:00 -0000 In-Reply-To: <20190210205616.GJ14180@gate.crashing.org> References: <25a0e5620b1e8a7a831ae9660c988f5dd98aa7dd.camel@aegee.org> <20181205171121.GQ3803@gate.crashing.org> <0990b8acd4cc08f74c1bf314851a113711dbfa04.camel@aegee.org> <20190206124401.GO14180@gate.crashing.org> <20190210205616.GJ14180@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/msg00741.txt.bz2 Hello Segher, the current procdure is: -- write at https://gcc.gnu.org/bugzilla/ -- read an answer, that the update shall be posted to gcc-patches -- subscribe to gcc-patches, post the change and wait for an answer. This waiting is not for free. There are a lot of emails, for the person might not be interested, but only waits for a reply on the own email. So after some time, I made filters sorting the emails from the mailing list, in order to make the waiting cheaper. -- at https://www.gnu.org/software/gcc/contribute.html is written “If you do not receive a response to a patch that you have submitted within two weeks or so, it may be a good idea to chase it by sending a follow-up email to the same list(s).” Because it is written that reminders are..., I have sent a reminder. > > If yes, how do you propose to proceed, so that a no-reminders-are-necessary-state is reached? > > Keep things as is? Reminders already are not necessary. > This statement does not align with the aforementioned webpage. The optimal way will be, if a bug/patch is filled in bugzilla and nothing more is necessary from the reporter. Postgres sends bugs collected over website over a mailing list. Regards Дилян On Sun, 2019-02-10 at 14:56 -0600, Segher Boessenkool wrote: > Hi Dilyan, > > On Sun, Feb 10, 2019 at 02:45:02PM +0000, Дилян Палаузов wrote: > > Do you share the opinion, that whatever can be done after receiving a reminder, can be arranged also without reminder? > > Yes. When people have time for it, they can trivially check what PRs are > still open that they are involved in. > > > If yes, how do you propose to proceed, so that a no-reminders-are-necessary-state is reached? > > Keep things as is? Reminders already are not necessary. > > If you want more attention given to the bugs you are involved in, you can > hire people to do that, or file reports for more interesting bugs, or make > your bug reports easier to work with. > > Since GCC has one major release every year, handling less urgent bugs can > take up to a year as well. > > > 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. > > The point is that automated reminders for PRs *are spam*. > > > Segher