From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23827 invoked by alias); 18 Nov 2006 11:00:31 -0000 Received: (qmail 23815 invoked by uid 22791); 18 Nov 2006 11:00:29 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 18 Nov 2006 11:00:18 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-68-107.inter.net.il [80.230.68.107]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id FFI47053 (AUTH halo1); Sat, 18 Nov 2006 13:00:08 +0200 (IST) Date: Sat, 18 Nov 2006 11:00:00 -0000 Message-Id: From: Eli Zaretskii To: Daniel Jacobowitz CC: nickrob@snap.net.nz, vladimir@codesourcery.com, gdb-patches@sources.redhat.com In-reply-to: <20061117210501.GA13104@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 17 Nov 2006 16:05:01 -0500) Subject: Re: MI: frozen variable objects Reply-to: Eli Zaretskii References: <17756.56523.353271.828046@kahikatea.snap.net.nz> <20061116220029.GA28461@nevyn.them.org> <17756.60994.909354.46765@kahikatea.snap.net.nz> <20061117151857.GB31319@nevyn.them.org> <17758.8216.142597.547417@kahikatea.snap.net.nz> <20061117210501.GA13104@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00198.txt.bz2 > Date: Fri, 17 Nov 2006 16:05:01 -0500 > From: Daniel Jacobowitz > Cc: Vladimir Prus , gdb-patches@sources.redhat.com > > > > If the changes go in after the release I generally have six months to spot a > > bug, if they go in now I'll have roughly two weeks. > > I don't get the fuss. It's not an immensely destabilizing change or a > huge new subsystem. Why should it be treated separately from any other > patch posted in the last few months, in the later half of a release > gap? Two weeks does seem a tad too short, much shorter than ``the last few months''. While you are right that the change is not immensely destabilizing, I'm sure you can understand Nick's concern for the quality of the released GDB, even if only in relatively minor features. > Let me be perfectly clear about this. I can spend a certain amount of > my work time reviewing community patches, because my employer is very > understanding about the FSF development process. I'm lucky in that > respect and hopefully so is GDB. Yes, we are extremely lucky that we have you, Daniel, and that you can do such a wonderful job for so many hours a day. I'm sure Nick didn't mean any disrespect. > And more maintainers. Absolutely. Any suggestions welcome. > All: Should Nick be an MI maintainer now? I vote in favor.