From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: Bob's MI objective
Date: Fri, 08 Oct 2004 13:42:00 -0000 [thread overview]
Message-ID: <01c4ad39$Blat.v2.2.2$9d15a8c0@zahav.net.il> (raw)
In-Reply-To: <20041008121321.GB15978@white> (message from Bob Rossi on Fri, 8 Oct 2004 08:13:21 -0400)
> Date: Fri, 8 Oct 2004 08:13:21 -0400
> From: Bob Rossi <bob@brasko.net>
> Cc: cagney@gnu.org, gdb@sources.redhat.com
>
> OK, Andrew gave me the exact opposite answer here. That is why I asked again
> http://sources.redhat.com/ml/gdb/2004-10/msg00177.html
>
> maybe I'm wrong, and you guys are saying the same thing?
It surely sounds like Andrew is saying that all versions of MI except
the latest one are completely unsupported and broken, but I really
doubt he meant that. After all, if that were the case, why would we
bother to keep those older versions in GDB?
But please wait for Andrew's definitive response.
> It is important to me that the CVS snapshots try to at least honor the
> last major MI version before the version bump. Is this something
> everyone thinks will be possible?
I think that an MI version that was just been superceded by a newer
one will not bitrot right away. So you can count on it for quite some
time. Also, all the tests for that version are still there to make
sure it works at least as well as it used to.
> I do understand that old MI protocols could be dropped because of
> maintenance issues. Would we go as far as dropping the last stable
> protocol, this could potentially be a problem for me.
I don't think the GDB maintainers will ever agree to such a radical
measure, even if someone were to suggest it.
next prev parent reply other threads:[~2004-10-08 13:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 20:13 Andrew Cagney
2004-10-06 22:36 ` Bob Rossi
2004-10-07 2:40 ` Andrew Cagney
2004-10-07 17:20 ` Bob Rossi
2004-10-07 20:50 ` Andrew Cagney
2004-10-07 22:42 ` Bob Rossi
2004-10-08 8:40 ` Fabian Cenedese
2004-10-08 13:17 ` Bob Rossi
2004-10-08 7:17 ` Bob Rossi
2004-10-08 12:41 ` Eli Zaretskii
2004-10-08 13:23 ` Bob Rossi
2004-10-08 13:42 ` Eli Zaretskii [this message]
2004-10-08 16:34 ` Daniel Jacobowitz
2004-10-08 16:28 ` Daniel Jacobowitz
2004-10-08 18:57 ` Eli Zaretskii
2004-10-09 11:14 ` Andrew Cagney
2004-10-10 4:06 ` Bob Rossi
2004-10-11 2:00 ` Bob Rossi
2004-10-11 14:12 ` Andrew Cagney
2004-10-11 17:22 ` Bob Rossi
2004-10-12 22:15 ` Michael Chastain
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='01c4ad39$Blat.v2.2.2$9d15a8c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--cc=cagney@gnu.org \
--cc=gdb@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