Hello Segher, my question was how do you propose to proceed, so that a no-reminders-for-patches-are-necessary-state is reached.
There is no relation with having infinite time or dealing with high-cost low-profit patches. Previously I raised the quesion, whether automating the process for sending reminders, is a good idea. This saves time of people to write reminders. Greetings Дилян On Mon, 2019-02-11 at 07:57 -0600, Segher Boessenkool wrote: > On Mon, Feb 11, 2019 at 12:44:31PM +0000, Дилян Палаузов wrote: > > -- 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).” > > That is about patches. Not about bugzilla. Sending reminders for bugzilla > reports is useless and annoying. Sending reminders for patches however is > necessary, the way our development works currently. It isn't clear any > change to procedures would help at all, since the fundamental problems need > to be attacked to make any progress. Maintainers do not have infinite time, > and there is no incentive to deal with high-cost low-profit patches. > > > Segher
