From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-24103-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 27490 invoked by alias); 27 Jan 2006 16:13:08 -0000
Received: (qmail 27478 invoked by uid 22791); 27 Jan 2006 16:13:08 -0000
X-Spam-Check-By: sourceware.org
Received: from eastrmmtao01.cox.net (HELO eastrmmtao01.cox.net) (68.230.240.38)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 27 Jan 2006 16:13:06 +0000
Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao01.cox.net           (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP           id <20060127161305.RTKS4894.eastrmmtao01.cox.net@localhost.localdomain>;           Fri, 27 Jan 2006 11:13:05 -0500
Received: from bob by localhost.localdomain with local (Exim 4.52) 	id 1F2WEH-0000Xj-0u; Fri, 27 Jan 2006 11:13:41 -0500
Date: Fri, 27 Jan 2006 17:00:00 -0000
From: Bob Rossi <bob@brasko.net>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: MI -break-info command issues
Message-ID: <20060127161340.GC30826@brasko.net>
Mail-Followup-To: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
References: <dr5csi$bg2$1@sea.gmane.org> <dr9s4n$rsf$1@sea.gmane.org> <ulkx2en42.fsf@gnu.org> <200601271115.22939.ghost@cs.msu.su> <ufyn9euj6.fsf@gnu.org> <drdchc$672$1@sea.gmane.org> <20060127151220.GA978@nevyn.them.org> <drdfb3$kpb$1@sea.gmane.org> <20060127155132.GA8843@nevyn.them.org> <drdgkk$qt1$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <drdgkk$qt1$1@sea.gmane.org>
User-Agent: Mutt/1.5.9i
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2006-01/txt/msg00303.txt.bz2

On Fri, Jan 27, 2006 at 07:09:56PM +0300, Vladimir Prus wrote:
> Daniel Jacobowitz wrote:
> 
> >> The problem with existing frontends can probably be solved by posting a
> >> prominent message to mailing list whenever MI output is going to change.
> >> Or using versioning.
> > 
> > This has been discussed before plenty of times.  We will make
> > incompatible changes to MI from time to time; but IMO that doesn't
> > justify making _unnecessary_ incompatible changes.
> > 
> > Like Bob, I wouldn't have added the fields.  But since they are
> > present, I see no reason to remove them.
> 
> Ok, understood. It would be good, though, if MI docs contained some
> introduction chapter that would state this policy. That'd prevented this
> thread from ever starting.

Hi Volodya,

It would be great if you could come up with some text that described the
problem. We could improve it here, and then add it to the manual.

Bob Rossi