Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: rms@gnu.org, drow@false.org, gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Wed, 20 Feb 2008 20:57:00 -0000	[thread overview]
Message-ID: <u7igzjt4s.fsf@gnu.org> (raw)
In-Reply-To: <20080220190512.4550A8FC6D@kahikatea.snap.net.nz> (message from 	Nick Roberts on Thu, 21 Feb 2008 08:05:12 +1300 (NZDT))

> From: Nick Roberts <nickrob@snap.net.nz>
> Cc: drow@false.org, gdb@sourceware.org
> Date: Thu, 21 Feb 2008 08:05:12 +1300 (NZDT)
> 
> 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.

> It looks like I've been outmanoeuvred

You make it sound like there were some kind of courtyard intrigues.
As someone who was part of the discussions, let me assure you that
nothing could be farther from the truth.  I hope at least my word is
still worth enough in your eyes to convince you that no hostile intent
or attitude were involved or expressed at any time, by anyone.

> 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; no one says that MI must be maintained by a single individual.
For all Vladimir's expertise, the experience you have gathered by
developing and maintaining the Emacs GDB UI front end is unique and
important, both to GDB and to Emacs.  We will not be willing to give
up your experience and knowledge lightly.

Thanks, and keep up the good work.


  reply	other threads:[~2008-02-20 20:00 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 [this message]
2008-02-20 21:20         ` Nick Roberts
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=u7igzjt4s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=nickrob@snap.net.nz \
    --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