From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, drow@false.org, gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Wed, 20 Feb 2008 21:20:00 -0000 [thread overview]
Message-ID: <18364.37907.135913.269853@kahikatea.snap.net.nz> (raw)
In-Reply-To: <u7igzjt4s.fsf@gnu.org>
> > Clearly Vladimir's appointment should be seen as an endorsement of his
> > views.
>
> No, it is not. GDB global maintainers are not appointed based on
> their views, they are appointed based on their coding and social
> skills. Unfortunately for you, your reaction to Vladimir's
> appointment puts you farther from a similar appointment, not closer.
Hopefully their views are taken into account. It doesn't sound like
I was very close, in the first place.
Having refused to revert changes that broke Emacs use of Gdb (albeit with
"undocumented assumptions") for the last three months, I find it disingenuous
for him to suddenly offer to fix parts now. I'm not optimistic about the
future, when the heat has died down.
>...
> > and perhaps I shouldn't be such a sore loser. I guess it's
> > checkmate and game over.
>
> You are not a loser, and this is not a game. This is not some kind of
> final verdict in high court without right to appeal, either. If you
> can accept friendly constructive criticism and change, there's no
> reason not to invite you to become a global maintainer at some later
> date;
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.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-02-20 20:57 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 [this message]
2008-02-20 21:50 ` Joel Brobecker
2008-02-20 23:25 ` Frank Ch. Eigler
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=18364.37907.135913.269853@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=rms@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