Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [Commit] New file
Date: Fri, 28 May 2004 19:52:00 -0000	[thread overview]
Message-ID: <16567.38968.219077.271649@nick.uklinux.net> (raw)
In-Reply-To: <6654-Fri28May2004105116+0300-eliz@gnu.org>

 > The situation I fear is that the latest gdb-mi.el will not work with a
 > recent Emacs release.  We already had that with gdba.el, remember?

Sure, it will be difficult to keep everything in sync but I think that if you
note the similarities between gdb-mi.el to gdba.el it is also important to
note the differences.  Unlike you, I don't have the benefit of first hand
experience but this is what I have inferred. gdba.el was written by Tom Lord
and Jim Kingdon (both then at Cygnus) and was based on a very early version of
gud.el which, in turn, was written by Eric Raymond and modified by others. As
far as I can see, there was no communication between the original two parties,
and those Emacs developers either did not know about level 2 annotations or
chose not to use them. So could gdba.el could be called a fork. That is not
the intention with gdb-mi.el, indeed the reverse is true, it is trying to pull
things together.

Nick


  reply	other threads:[~2004-05-28 19:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 20:07 Nick Roberts
2004-05-25 22:36 ` Andrew Cagney
2004-05-26  9:54   ` Eli Zaretskii
2004-05-26  9:51 ` Eli Zaretskii
2004-05-26 16:45   ` Andrew Cagney
2004-05-27  7:23     ` Eli Zaretskii
2004-05-27 20:19       ` Andrew Cagney
2004-05-28  7:54         ` Eli Zaretskii
2004-05-28 19:52           ` Nick Roberts [this message]
2004-05-31 19:07             ` Andrew Cagney
2004-06-01  4:35               ` Eli Zaretskii
2004-06-01 20:09                 ` Nick Roberts
2004-06-01 22:21                   ` Eli Zaretskii
2004-05-26 20:43   ` Nick Roberts

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=16567.38968.219077.271649@nick.uklinux.net \
    --to=nickrob@gnu.org \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --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