From: fche@redhat.com (Frank Ch. Eigler)
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Wed, 20 Feb 2008 23:25:00 -0000 [thread overview]
Message-ID: <y0mskznqp66.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <18364.37907.135913.269853@kahikatea.snap.net.nz> (Nick Roberts's message of "Thu, 21 Feb 2008 09:56:51 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> [...] Thanks for your support but after six years of contributing
> and peer reviewing patches the thought that "if I keep trying, I too
> might one day become a maintainer" doesn't really excite me.
Please don't be disappointed by mere politics. If your technical
contributions continue, and are robustly constructed and justified,
any reasonable maintainer will have no choice but to go along. A
powerful contributor can outproduce a maintainer, and in the end
that's what matters.
- FChE
next prev parent reply other threads:[~2008-02-20 21:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 19:37 Daniel Jacobowitz
2008-02-19 20:29 ` Nick Roberts
2008-02-19 20:46 ` Daniel Jacobowitz
2008-02-19 20:47 ` Nick Roberts
2008-02-21 1:43 ` Daniel Jacobowitz
2008-02-20 3:12 ` Bob Rossi
2008-02-20 8:59 ` Richard Stallman
2008-02-21 21:37 ` Bob Rossi
2008-02-20 19:05 ` Richard Stallman
2008-02-20 20:00 ` Nick Roberts
2008-02-20 20:57 ` Eli Zaretskii
2008-02-20 21:20 ` Nick Roberts
2008-02-20 21:50 ` Joel Brobecker
2008-02-20 23:25 ` Frank Ch. Eigler [this message]
2008-02-22 3:34 ` Nick Roberts
2008-02-22 17:37 ` Thomas Dineen
2008-02-22 22:09 ` Eli Zaretskii
2008-02-22 22:14 ` Christopher Faylor
2008-02-22 22:23 ` Bob Rossi
2008-02-23 0:01 ` Dave Korn
2008-02-23 0:58 ` Alpár Jüttner
2008-02-23 8:16 ` Jim Blandy
2008-02-23 11:13 ` Nick Roberts
2008-02-23 11:15 ` Eli Zaretskii
2008-02-23 12:34 ` Eli Zaretskii
2008-02-22 23:36 ` Jim Blandy
2008-02-21 19:25 ` Stan Shebs
2008-02-22 4:08 ` Nick Roberts
2008-02-22 2:52 ` Bob Rossi
2008-02-22 8:43 ` Vladimir Prus
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=y0mskznqp66.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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