From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-43931-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 11813 invoked by alias); 5 May 2006 15:46:38 -0000
Received: (qmail 11794 invoked by uid 22791); 5 May 2006 15:46:37 -0000
X-Spam-Check-By: sourceware.org
Received: from eastrmmtao06.cox.net (HELO eastrmmtao06.cox.net) (68.230.240.33)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 05 May 2006 15:46:36 +0000
Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao06.cox.net           (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP           id <20060505144812.JJUX16402.eastrmmtao06.cox.net@localhost.localdomain>;           Fri, 5 May 2006 10:48:12 -0400
Received: from bob by localhost.localdomain with local (Exim 4.52) 	id 1Fc1bn-0003QI-I2; Fri, 05 May 2006 10:48:43 -0400
Date: Fri, 05 May 2006 15:46:00 -0000
From: Bob Rossi <bob_rossi@cox.net>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: -stack-list-frames HIGH_FRAME changes
Message-ID: <20060505144843.GA10374@brasko.net>
Mail-Followup-To: Vladimir Prus <ghost@cs.msu.su>, 	Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
References: <e3f0b0$ldg$1@sea.gmane.org> <20060505135124.GA27371@nevyn.them.org> <200605051838.20652.ghost@cs.msu.su>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200605051838.20652.ghost@cs.msu.su>
User-Agent: Mutt/1.5.9i
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2006-05/txt/msg00060.txt.bz2

> > Please don't add new tests to just mi2-stack.exp.  I don't much care
> > whether mi2-stack.exp is updated or not, but when we finalize mi3 and
> > create mi3-* tests, they're going to be copied from mi-*.  So it's
> > important that new tests go there also.
> 
> So, what's the point of mi2 tests at all? 
> In any case, there's revised patch:

The mi- tests are the "current" MI tests. The mi2- tests make sure that
gdb -i=mi2 work. 

So, at some point in the future we will make mi- tests become mi3-, we
will still have mi2- and mi- will become the new "current" MI tests.

Bob Rossi