From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch rfa:doco rfc:NEWS] mi1 -> mi2; rm mi0
Date: Mon, 30 Sep 2002 15:36:00 -0000 [thread overview]
Message-ID: <20020930223229.GA30594@nevyn.them.org> (raw)
In-Reply-To: <3D98CAEA.7000304@redhat.com>
On Mon, Sep 30, 2002 at 06:06:34PM -0400, Andrew Cagney wrote:
>
> >>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.
OK. My logic went like:
It would be nice to be able to use a snapshot, which has
non-MI-syntax-related improvements and fixes in it, without having to
handle a changing interface.
But we can already do that: they use -i=mi1. So it's all good.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-09-30 22:36 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
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 [this message]
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=20020930223229.GA30594@nevyn.them.org \
--to=drow@mvista.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