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 clear, when contributions will be ignored
Date: Wed, 06 Feb 2019 12:46:00 -0000	[thread overview]
Message-ID: <20190206124401.GO14180@gate.crashing.org> (raw)
In-Reply-To: <0990b8acd4cc08f74c1bf314851a113711dbfa04.camel@aegee.org>

On Fri, Dec 07, 2018 at 10:55:11AM +0000, Дилян Палаузов wrote:
> will it help, if Bugzilla is reprogrammed to send automatically weekly
> reminders on all patches, that are not integrated yet?

No, that will not help.

If an interested party sends a friendly ping, that is of course welcome.
But automated pings are spam: unwanted bulk mail.

> The patch I proposed on 27th Oct was first submitted towards GDB and
> then I was told to send it to GCC.  Here I was told to sent it to GDB. 
> What shall happen to quit the loop?

You can cc: both sides of the discussion.  Either also gdb-patches, or also
whoever told you to send it to GCC instead, or both.  And include a link to
the mailing list archive of your thread on gdb-patches in your mail to
gcc-patches, so that all parties can see the relevant context.  Make it
easy for people to help you!


Segher

  parent reply	other threads:[~2019-02-06 12:46 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 [this message]
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=20190206124401.GO14180@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).