public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Make clear, when contributions will be ignored
Date: Sun, 10 Feb 2019 20:59:00 -0000	[thread overview]
Message-ID: <20190210205616.GJ14180@gate.crashing.org> (raw)
In-Reply-To: <a7f5412515a1698e47c006703519e490c7522047.camel@aegee.org>

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

  reply	other threads:[~2019-02-10 20:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  7:36 Make claer, " Дилян Палаузов
2018-12-05 17:13 ` Segher Boessenkool
2018-12-05 17:37   ` Joseph Myers
2018-12-07 10:55     ` Make clear, " Дилян Палаузов
2018-12-21  8:08       ` +reminder+ " Дилян Палаузов
2019-02-05 13:36       ` Дилян Палаузов
2019-02-05 23:10         ` Joseph Myers
2019-02-06 12:46       ` Segher Boessenkool
2019-02-10 14:45         ` Дилян Палаузов
2019-02-10 20:59           ` Segher Boessenkool [this message]
2019-02-11 12:44             ` Дилян Палаузов
2019-02-11 14:01               ` Segher Boessenkool
2019-02-11 14:16                 ` Дилян Палаузов
2019-02-11 16:27                   ` Segher Boessenkool
2019-02-17 17:00                     ` Дилян Палаузов
2019-02-17 19:13                       ` Segher Boessenkool
2019-02-17 19:47                         ` Дилян Палаузов
2018-12-05 17:17 ` Make claer, " Maciej W. Rozycki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190210205616.GJ14180@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=dilyan.palauzov@aegee.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).