From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19852 invoked by alias); 4 Oct 2004 20:54: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 19843 invoked from network); 4 Oct 2004 20:54:00 -0000 Received: from unknown (HELO capitol.mail.pas.earthlink.net) (207.217.120.180) by sourceware.org with SMTP; 4 Oct 2004 20:54:00 -0000 Received: from ip216-26-76-19.dsl.du.teleport.com ([216.26.76.19] helo=stray.canids) by capitol.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1CEZqJ-0004Yr-00 for gdb@sources.redhat.com; Mon, 04 Oct 2004 13:53:59 -0700 Received: from stray.canids (localhost.localdomain [127.0.0.1]) by stray.canids (Postfix) with ESMTP id 1FBCD502AB6 for ; Mon, 4 Oct 2004 13:53:57 -0700 (PDT) From: Felix Lee To: gdb@sources.redhat.com Subject: Re: GDB/MI snapshots between major release's References: <20041003163918.GB7030@white> <01c4a9ce$Blat.v2.2.2$d01969a0@zahav.net.il> <20041004131906.GB8121@white> <20041004145921.BAC77502AB6@stray.canids> <20041004154928.GE8121@white> <20041004160455.DD23A502AB6@stray.canids> <20041004164803.GG8121@white> <20041004181201.9A8E9502AB6@stray.canids> <20041004183145.GH8121@white> In-Reply-To: <20041004183145.GH8121@white> on Mon, 04 Oct 2004 14:31:46 EDT from Bob Rossi Date: Mon, 04 Oct 2004 21:07:00 -0000 Message-Id: <20041004205357.1FBCD502AB6@stray.canids> X-SW-Source: 2004-10/txt/msg00061.txt.bz2 Bob Rossi : > T1 GDB 7.0 has MI10 (official) > T2 GDB 7.0-CVS has MI11 (unofficial, because of MI incompatible change X1 ) > T3 GDB 7.0-CVS has MI11 (unofficial, because of MI incompatible change X2 ) > T4 GDB 7.1 has MI11 (official) why would that happen? I expect 'create a new MI version' to be basically an atomic change. like, someone experiments with MI11 on a branch, then merges it into the trunk when it's stable and tests reasonable cleanly. if the incompatible change is simple enough to be done in the trunk, then updating the version and the testsuite should be part of the same commit. --