From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6225 invoked by alias); 30 Aug 2006 02:33:42 -0000 Received: (qmail 6216 invoked by uid 22791); 30 Aug 2006 02:33:41 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 30 Aug 2006 02:33:37 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GIFtX-0001fr-Dj; Tue, 29 Aug 2006 22:33:35 -0400 Date: Wed, 30 Aug 2006 02:33:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: gdb@sources.redhat.com Subject: Re: Merge of nickrob-async-20060513 to mainline? Message-ID: <20060830023335.GA6377@nevyn.them.org> Mail-Followup-To: Nick Roberts , gdb@sources.redhat.com References: <17652.63229.637451.185345@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17652.63229.637451.185345@kahikatea.snap.net.nz> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00231.txt.bz2 On Wed, Aug 30, 2006 at 02:25:01PM +1200, Nick Roberts wrote: > > I have recently updated/merged the asynchronous branch (nickrob-async-20060513) > that I am working on. The overall task is too great for me to complete alone > and it has attracted no interest as a branch. For these reasons (and the > coming release of Emacs 22) I would like to merge it with mainline GDB. I have > tried to arrange that GDB on my branch will only build with the "--async" > option for GNU/Linux on i386. This should mean that it should build and run as > before on any other platform, and that itwill only run differently on > i386-linux-gnu if the "--async" option is specified. > > If it passes the current testsuite and I add some new testcases for the > asynchronous operation (probably in the MI part of the testsuite), may I make > such a merge? Could you remind me what this has to do with the release of emacs 22? I'm not sure what interest you expected to generate on a branch, which you didn't discuss on any of the mailing lists; as a rule, no one has time to check out and poke at projects that no one tells them about. The last time I heard status from you on the branch, it wasn't working. I gather it's better off now. That makes it much more interesting. I think that merging it in without review would be at the least unwise. How big are the changes relative to mainline (diffstat)? Is there an angle from which we can start looking at them? -- Daniel Jacobowitz CodeSourcery