Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Alpár Jüttner" <alpar@cs.elte.hu>
Cc: gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Sat, 23 Feb 2008 11:15:00 -0000	[thread overview]
Message-ID: <umypshqo6.fsf@gnu.org> (raw)
In-Reply-To: <1203724876.4440.70.camel@piko.site> (message from 	=?ISO-8859-1?Q?Alp=E1r_J=FCttner?= on Sat, 23 Feb 2008 01:01:16 +0100)

> From: =?ISO-8859-1?Q?Alp=E1r_J=FCttner?= <alpar@cs.elte.hu>
> Cc: gdb@sourceware.org
> Date: Sat, 23 Feb 2008 01:01:16 +0100
> 
> I think, the real issue is not the openness of the project management,
> but this:
> 
> > Given that I have made significant contributions
> > to GDB/MI over a long period of time then it would then seem appropriate to at
> > least e-mail me off-list before the announcement to inform me of your
> > intention.
> 
> As far as I see, nobody has commented on this sentence of Nick.

Actually, that's not true.  Daniel did respond:

> > Date: Wed, 20 Feb 2008 20:41:47 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb@sourceware.org, Richard Stallman <rms@gnu.org>
> > 
> > On Wed, Feb 20, 2008 at 09:46:04AM +1300, Nick Roberts wrote:
> > > was interested in the role.  Given that I have made significant contributions
> > > to GDB/MI over a long period of time then it would then seem appropriate to at
> > > least e-mail me off-list before the announcement to inform me of your
> > > intention.
> > 
> > Yes.  I didn't handle the announcement well, and I should have avoided
> > the (untrue) appearance of conflict of interest by asking someone else
> > to make the announcement.

I think that's an appropriate response.

> Some people expected an apology in this thread but nobody seemed to be
> thinking about whether he should apologize. More than one person made a
> mistake in this awkward story. I strongly believe that a frank 'sorry'
> from the one who made the first one would be followed by others.

I think the above comes as close to "sorry" as one can expect in such
situations.


  parent reply	other threads:[~2008-02-23 11:13 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
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 [this message]
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=umypshqo6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=alpar@cs.elte.hu \
    --cc=gdb@sourceware.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