From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25961 invoked by alias); 2 Sep 2008 10:22:44 -0000 Received: (qmail 25945 invoked by uid 22791); 2 Sep 2008 10:22:44 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 02 Sep 2008 10:22:09 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id m82AKjZF003996; Tue, 2 Sep 2008 12:20:45 +0200 (CEST) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id m82AKiN8013408; Tue, 2 Sep 2008 12:20:44 +0200 (CEST) Date: Tue, 02 Sep 2008 10:22:00 -0000 Message-Id: <200809021020.m82AKiN8013408@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: uweigand@de.ibm.com CC: gdb-patches@sourceware.org In-reply-to: <200809011856.m81IufC2012091@d12av02.megacenter.de.ibm.com> (uweigand@de.ibm.com) Subject: Re: [rfc][00/37] Eliminate builtin_type_ macros References: <200809011856.m81IufC2012091@d12av02.megacenter.de.ibm.com> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-09/txt/msg00012.txt.bz2 > Date: Mon, 1 Sep 2008 20:56:41 +0200 (CEST) > From: "Ulrich Weigand" > > Mark Kettenis wrote: > > > I've probably had one piwo too many at this point, but can we please > > stop this Linux [x/zillion] crap? You can't seriously pretend there > > are really 37 independent diffs that people would want to review > > and/or test can you? > > Actually, the patches *do* touch mostly independent areas of GDB, > and I'd expect different maintainers to want to review only some > of them. I've spent some effort to try to separate out functional > changes, in the hope of making review simpler ... Let me say that even if I think it doesn't really help, I apreciate the effort. > As to *testing*, I agree that having to apply 37 patches in sequence > is a pain, which is why I sent -in addition to the broken-out series- > a single cumulative patch as well. Yes, that was a good thing to do. I apologize for sending the message I sent yesterday evening before reading all my mail. > In the end, this is simply a large set of changes (the cumulative patch > is 8000 lines, the broken-out patches total 10000 lines) spread out > across many parts of GDB (the patch set touches 97 files) -- if you have > suggestions how to present a change like this in a way that's easier to > review, those would certainly be welcome. I don't think there is much you can do about it. A large set of fairly mechanical changes is simply a large set of mechanical changes. It's probably good if people have a look at part of the diff, but in the end we'll just have to trust that the job was done properly and that it gets committed (preferably after people have tested it).