From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7583 invoked by alias); 5 Mar 2005 11:28:00 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7479 invoked from network); 5 Mar 2005 11:27:46 -0000 Received: from unknown (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org with SMTP; 5 Mar 2005 11:27:46 -0000 Received: from zaretski (tony03-38-103.inter.net.il [80.230.38.103]) by romy.inter.net.il (MOS 3.5.6-GR) with ESMTP id ARC55401 (AUTH halo1); Sat, 5 Mar 2005 13:27:32 +0200 (IST) Date: Sat, 05 Mar 2005 11:28:00 -0000 From: "Eli Zaretskii" To: Bob Rossi Message-ID: <01c52176$Blat.v2.4$311d79c0@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: gdb@sources.redhat.com In-reply-to: <20050304221656.GD2419@white> (message from Bob Rossi on Fri, 4 Mar 2005 17:16:56 -0500) Subject: Re: patch review time Reply-to: Eli Zaretskii References: <20050303150022.GD32613@white> <01c5208c$Blat.v2.4$989a81a0@zahav.net.il> <20050304142600.GA2419@white> <01c520d0$Blat.v2.4$bbe28c40@zahav.net.il> <20050304155441.GC2419@white> <01c520e0$Blat.v2.4$f07527a0@zahav.net.il> <20050304221656.GD2419@white> X-SW-Source: 2005-03/txt/msg00043.txt.bz2 > Date: Fri, 4 Mar 2005 17:16:56 -0500 > From: Bob Rossi > Cc: gdb@sources.redhat.com > > The only possible solution I could come to, was that he thought patch > review would slow him down to the point were he wouldn't be able to get > work done. This cannot be true if the patch review takes hours. Even working in his unilateral commit-whenever-you-want paradigm, Andrew could only commit a patch once in a couple of days--this is more than enough for me and others to review the previous patch. > Even though you think this isn't the problem, it's the only > conclusion I can draw from his statement. You could draw the conclusion I drew: that Andrew simply doesn't want to fix whatever problematic issues I and others pointed out in his patches, and doesn't want to be bothered to explain and defend his design. > > > Well what should I do? > > > > The only thing to do is to bug the responsible maintainer(s). > > What if the particular maintainer is busy? You should complain to the head maintainer.