public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
To: Segher Boessenkool <segher@kernel.crashing.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, 17 Feb 2019 19:47:00 -0000	[thread overview]
Message-ID: <8c341371bae0ddb911c936f2246a72b04aa540c8.camel@aegee.org> (raw)
In-Reply-To: <20190217190944.GI14180@gate.crashing.org>

Hello Segher,

On Sun, 2019-02-17 at 13:09 -0600, Segher Boessenkool wrote:
> On Sun, Feb 17, 2019 at 04:59:40PM +0000, Дилян Палаузов wrote:
> > My point is to reorgnize the approach in such a way, that sending reminders gets irrelevant (has no impact) and
> > therefore not necessary.
> > 
> > Currently priority is given to submitters who send reminders, irrespective of the properties a patch has.
> 
> No, that is not true for many reviewers.  It is however true that patches
> that are *not* pinged (say, once a week) often are forgotten, or the
> maintainer assumes the patch is not wanted anymore, etc.

The assumption that an unpinged patch is not wanted any more is obviously wrong.  The assumption shall be, that people
who do not send reminders have not read, that they are supposed to send reminers, as these people assume that sending
reminders makes no difference.

If this is not true for many reviewers, why does sending reminder then make a difference and the webpage advices to send
reminders?  

To sum up, sending a reminder on a subject and the subject (patch being good/bad/excellent/inappropriate/messy) are two
different things.  I am talking here about the necessity for sending reminders, irrespective of the subject/properties a
patch has.

Regards
  Дилян

  reply	other threads:[~2019-02-17 19:47 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
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                         ` Дилян Палаузов [this message]
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=8c341371bae0ddb911c936f2246a72b04aa540c8.camel@aegee.org \
    --to=dilyan.palauzov@aegee.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=segher@kernel.crashing.org \
    /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).