From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32355 invoked by alias); 12 Aug 2004 19:00:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 32332 invoked from network); 12 Aug 2004 19:00:14 -0000 Received: from unknown (HELO aragorn.inter.net.il) (192.114.186.23) by sourceware.org with SMTP; 12 Aug 2004 19:00:14 -0000 Received: from zaretski ([80.230.146.88]) by aragorn.inter.net.il (MOS 3.4.6-GR) with ESMTP id EEI09004; Thu, 12 Aug 2004 21:59:25 +0300 (IDT) Date: Thu, 12 Aug 2004 19:00:00 -0000 From: "Eli Zaretskii" To: Andrew Cagney Message-Id: <2914-Thu12Aug2004215629+0300-eliz@gnu.org> CC: gdb-patches@sources.redhat.com In-reply-to: <411B65D0.1040900@gnu.org> (message from Andrew Cagney on Thu, 12 Aug 2004 08:42:56 -0400) Subject: Re: [PATCH] Improve i386 prologue analyzer Reply-to: Eli Zaretskii References: <200408012158.i71LwpRw033840@elgar.kettenis.dyndns.org> <3405-Mon02Aug2004070159+0300-eliz@gnu.org> <410EAFBB.5080102@gnu.org> <2914-Tue03Aug2004065313+0300-eliz@gnu.org> <200408061933.i76JX3HJ008032@elgar.kettenis.dyndns.org> <4113EA3B.3000900@gnu.org> <2914-Sat07Aug2004183455+0300-eliz@gnu.org> <41150161.3000306@gnu.org> <41155A83.nail9VC11PTRT@mindspring.com> <7704-Sun08Aug2004065437+0300-eliz@gnu.org> <4115FF44.nail59F11C8I0@mindspring.com> <200408081108.i78B8Cpk009362@elgar.kettenis.dyndns.org> <411633BE.2010809@gnu.org> <7137-Sun08Aug2004223001+0300-eliz@gnu.org> <4116AEA1.7060900@gnu.org> <2914-Mon09Aug2004220629+0300-eliz@gnu.org> <411961FC.4010007@gnu.org> <6654-Wed11Aug2004065005+0300-eliz@gnu.org> <411A53C6.3020906@gnu.org> <8011-Wed11Aug2004205209+0300-eliz@gnu.org> <411B65D0.1040900@gnu.org> X-SW-Source: 2004-08/txt/msg00471.txt.bz2 > Date: Thu, 12 Aug 2004 08:42:56 -0400 > From: Andrew Cagney > > Please, please, articulate the `pain on our part' that we're apparently > all suffering. I'm the release manager, if anyone is is going to > experience pain, it's going to be me. Yes, and I don't think we should dismiss your pain (==loss of time) so easily. > > It's also the pain of our users > > who will need to install two versions within 4 weeks. > > This update is for _MIPS_ users only. The next update is for _i386_ > users only. What about people (or sysadmins) who need both, e.g. because they actually make a good use of the multi-arch features and debug several different CPUs from the same system? Anyway, those are not the important issues here. > > And I still don't understand what is the rush to release the MIPS > > patch without waiting for another week or two and then releasing the > > i386 patch as well. > > If I were a MIPS user (hmm, I'm even the maintainer), I'd be pretty > cheesed off that a fix to get `break main; run' working was being held > back due the inistance that it be bundled with an unrelated i386 fix. Sorry, Andrew, this is just reiterating what I already said I didn't understand: if we care so much for the MIPS, why did you refuse to wait for it to be fixed in 6.2? And if 6.2 could hit the street with MIPS broken, why cannot it stay broken for a week or two more, instead of letting the i386 remain broken longer? I keep asking this same question for about eternity, and you keep not answering it, for some reason that is beyond me. It's embarrassing. If there is some logic that would show why these two decisions do not contradict each other, please explain that logic. You don't need my agreement to go ahead, but I think I deserve to at least know your reasoning, even if I disagree.