From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27737 invoked by alias); 30 Sep 2002 22:06:34 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27728 invoked from network); 30 Sep 2002 22:06:33 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 30 Sep 2002 22:06:33 -0000 Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 39142800152 for ; Mon, 30 Sep 2002 18:06:33 -0400 (EDT) Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5883F3CB7; Mon, 30 Sep 2002 18:06:34 -0400 (EDT) Message-ID: <3D98CAEA.7000304@redhat.com> Date: Mon, 30 Sep 2002 15:06:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [patch rfa:doco rfc:NEWS] mi1 -> mi2; rm mi0 References: <3D974315.2050201@redhat.com> <20020929195533.GA5967@nevyn.them.org> <3D97603F.7080906@redhat.com> <20020929213757.GA9950@nevyn.them.org> <3D97749E.9020306@redhat.com> <20020930045522.GA28510@nevyn.them.org> <3D9867DB.4010607@redhat.com> <20020930151700.GA17849@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00783.txt.bz2 >> However, should the HEAD hold off on recognizing -i=mi2 until the next >> branch is cut? On the HEAD, -i=mi evolves by definition. However, >> -i=mi2 is evolving as well :-( > > > That'd be best I think. I think that -i=mi2 specifies a fixed standard > and we don't have one yet; so how about -i=mi being different from > -i=mi1, but not adding -i=mi2 until we're ready to fix the interface? I just looked, and I take the idea back. It means updating NEWS, DOC and testsuite twice - just after the branch (to start the new interface) and just before a branch (to freeze the new interface). I think its going to be easier to get it all done once just after the branch. If someone reports a bug against a YYYYMMDD version of GDB then it's pretty clear that they are not using a released GDB. Andrew