public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.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:17:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.21.1812051707170.7193@eddie.linux-mips.org> (raw)
In-Reply-To: <25a0e5620b1e8a7a831ae9660c988f5dd98aa7dd.camel@aegee.org>

On Wed, 5 Dec 2018, Дилян Палаузов wrote:

> 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.

1. You do not have a contract in place that would guarantee you any 
   specific timelines; if you want that, then hire someone to do the
   maintainer's duties for you.

2. Maintainers are volunteers working on the best-effort basis, and
   have other duties.

3. <https://sourceware.org/gdb/wiki/ContributionChecklist#Ping_and_keep_pinging>

4. Wrong mailing list for GDB matters.

 HTH,

  Maciej

      parent reply	other threads:[~2018-12-05 17:17 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
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 ` Maciej W. Rozycki [this message]

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=alpine.LFD.2.21.1812051707170.7193@eddie.linux-mips.org \
    --to=macro@linux-mips.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).