From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26305 invoked by alias); 5 Oct 2004 19:41:02 -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 26298 invoked from network); 5 Oct 2004 19:41:02 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 5 Oct 2004 19:41:02 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CEvBE-0002ye-3s; Tue, 05 Oct 2004 15:41:00 -0400 Date: Wed, 06 Oct 2004 01:01:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Bob Rossi , GDB Subject: Re: MI and backwards compatibility Message-ID: <20041005194100.GA4675@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Bob Rossi , GDB References: <20041001142517.GD4100@white> <4162F80C.4070409@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4162F80C.4070409@gnu.org> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-10/txt/msg00101.txt.bz2 On Tue, Oct 05, 2004 at 03:37:48PM -0400, Andrew Cagney wrote: > Other than ensuring that there's a reasonable overlap between EMACS and > GDB releases, I don't see how this is a GDB problem. Just keep in mind > that only the last offical MI release (currently gdb.mi/mi2-*) and > extensions added since then (gdb.mi/mi1-*) are being covered by GDB's > testsuite. ^^^^^^^^^^^^ You mean mi-*, right? That's the since-mi2 set. -- Daniel Jacobowitz