Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfa:doco rfc:NEWS] mi1 -> mi2; rm mi0
Date: Sun, 29 Sep 2002 21:55:00 -0000	[thread overview]
Message-ID: <20020930045522.GA28510@nevyn.them.org> (raw)
In-Reply-To: <3D97749E.9020306@redhat.com>

On Sun, Sep 29, 2002 at 05:46:06PM -0400, Andrew Cagney wrote:
> >On Sun, Sep 29, 2002 at 04:19:11PM -0400, Andrew Cagney wrote:
> >
> >>>On Sun, Sep 29, 2002 at 02:14:45PM -0400, Andrew Cagney wrote:
> >>>
> >
> >>>>Hello,
> >>>>
> >>>>The attached patch updates things so that "mi2" is the default MI 
> >>>>syntax.  I need to add a mechanism so that the MI code can query the 
> >>>>version but I'll post that separatly.
> >>>>
> >>>>It modifies NEWS (comments?).
> >>>>It updates the doco (ok?).
> >>>>
> >>>>Andrew
> >
> >>>
> >>>
> >>>It seems to me that this is going about everything backwards.
> >>>
> >>>There isn't an mi2 yet, is there?
> >
> >>
> >>Actually, I think "mi2" changes have been sneeking through for a while. 
> >> The attached, for instance, modifies [fixes] a commands output in a 
> >>way that isn't backward compatible.
> >
> >
> >Are you planning to revert mi1 then?
> 
> Que?

"mi2" changes have been sneaking in.  Are you planning to revert them -
create an "mi1" which matches what mi1 actually was.

Otherwise, where is the line drawn to mark the interface version as
final?  It seems to me that the default shouldn't be evolving, that
-i=mi should default to a fixed point until the next version is
running.

Maybe I'm wrong though.


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-09-30  4:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 11:14 Andrew Cagney
2002-09-29 12:55 ` Daniel Jacobowitz
2002-09-29 13:19   ` Andrew Cagney
2002-09-29 14:37     ` Daniel Jacobowitz
2002-09-29 14:46       ` Andrew Cagney
2002-09-29 21:55         ` Daniel Jacobowitz [this message]
2002-09-30  8:03           ` Andrew Cagney
2002-09-30  8:16             ` Daniel Jacobowitz
2002-09-30 15:06               ` Andrew Cagney
2002-09-30 15:36                 ` Daniel Jacobowitz
2002-09-29 22:01 ` Eli Zaretskii
2002-09-30 15:14   ` Andrew Cagney
2002-09-30 22:13     ` Eli Zaretskii
2002-10-01 14:26 ` Andrew Cagney
     [not found] <1033404264.17743.ezmlm@sources.redhat.com>
2002-09-30 17:48 ` Jim Ingham
2002-10-01  9:29   ` Andrew Cagney
2002-10-01 10:34     ` Jim Ingham
2002-10-01 13:25       ` Andrew Cagney
2002-10-01 14:01         ` Jim Ingham
2002-10-01 15:10           ` Andrew Cagney
2002-10-01 15:46             ` Jim Ingham
2002-10-01 16:39               ` Keith Seitz
2002-10-01 17:45                 ` Jim Ingham
2002-10-02  7:58                   ` Keith Seitz
2002-10-02 10:49                     ` Jim Ingham
2002-10-25 14:48                       ` Andrew Cagney
2002-10-01 23:25                 ` Jason Molenda
2002-10-02 10:22                 ` Stan Shebs
     [not found] <1035593825.16489.ezmlm@sources.redhat.com>
2002-10-25 18:22 ` Jim Ingham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020930045522.GA28510@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox