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: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Make claer, when contributions will be ignored
Date: Wed, 05 Dec 2018 17:13:00 -0000	[thread overview]
Message-ID: <20181205171121.GQ3803@gate.crashing.org> (raw)
In-Reply-To: <25a0e5620b1e8a7a831ae9660c988f5dd98aa7dd.camel@aegee.org>

Hi!

On Wed, Dec 05, 2018 at 07:36:09AM +0000, Дилян Палаузов wrote:
> on 27th October I sent to gcc-patches a mail with the subject “Don’t
> build gdb/readline/libreadline.a, when --with-system-readline is
> supplied”

The patch looks fine to me, fwiw.

> and on 14th November I sent a reminder.  I got no answer. 
> Before sending the emails I filled a bugzilla ticket.
> 
> Can you please make it clear, when contributions will be ignored, or
> agree on some procedures, where all contributions are handled in
> reasonable time withot reminders, in a way that the processes work
> reliably.

You can cc: people you think will be able to handle it.  You can ping
your patches regularly (say, every week).

Patches are usually ignored because everyone thinks someone else will
handle it.


Segher

  reply	other threads:[~2018-12-05 17:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  7:36 Дилян Палаузов
2018-12-05 17:13 ` Segher Boessenkool [this message]
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                         ` Дилян Палаузов
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=20181205171121.GQ3803@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=dilyan.palauzov@aegee.org \
    --cc=gcc-patches@gcc.gnu.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).