From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28833 invoked by alias); 23 Feb 2008 08:16:56 -0000 Received: (qmail 28822 invoked by uid 22791); 23 Feb 2008 08:16:55 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 23 Feb 2008 08:16:25 +0000 Received: from kahikatea.snap.net.nz (225.61.255.123.dynamic.snap.net.nz [123.255.61.225]) by viper.snap.net.nz (Postfix) with ESMTP id 03FDC3DA8DA; Sat, 23 Feb 2008 21:16:22 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 121DA8FC6D; Sat, 23 Feb 2008 21:16:16 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18367.54863.280395.555742@kahikatea.snap.net.nz> Date: Sat, 23 Feb 2008 11:13:00 -0000 To: =?ISO-8859-1?Q?Alp=E1r_J=FCttner?= Cc: gdb@sourceware.org Subject: RE: New MI maintainer In-Reply-To: <1203724876.4440.70.camel@piko.site> References: <18363.14758.855327.355215@kahikatea.snap.net.nz> <20080220190512.4550A8FC6D@kahikatea.snap.net.nz> <18364.37907.135913.269853@kahikatea.snap.net.nz> <18366.14530.875406.113087@kahikatea.snap.net.nz> <47BF0478.1050209@ix.netcom.com> <20080222220927.GA21434@ednor.casa.cgf.cx> <20080222222124.GH26716@brasko.net> <007a01c875ab$aae85770$2e08a8c0@CAM.ARTIMI.COM> <1203724876.4440.70.camel@piko.site> X-Mailer: VM 7.19 under Emacs 22.1.90.4 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-02/txt/msg00201.txt.bz2 > 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. Thanks. I don't really want an apology from anyone (just as I would rather not apologise) but I appreciate you pointing out other contributory factors. I now know more than I did at the start of the thread and the only thing I would add is that I think such appointments are announced by a member of the GDB Steering Committee who are "not generally involved in day-to-day development" (not the release manager) starting with something like: "After careful consideration the GDB Steering Committee are glad to announce..." to make it clear that the appointment has been made collectively. I'm starting to feel uncomfortable with this thread now so I'd like it to stop (just as the majority of silent subscribers probably would too). One chapter ends and a new one begins. -- Nick http://www.inet.net.nz/~nickrob