From: nickrob@snap.net.nz (Nick Roberts)
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Delete gdb-mi.el
Date: Fri, 25 Sep 2009 11:02:00 -0000 [thread overview]
Message-ID: <19132.41804.225362.342372@totara.tehura.co.nz> (raw)
In-Reply-To: <83zl8jtnpr.fsf@gnu.org>
> > CVS Emacs now uses GDB/MI directly so this file is no longer
> > relevant and I would to remove it.
>
> People who use CVS Emacs do not necessarily use CVS GDB, and vice
> versa.
The file in the GDB repository had the same name as the one in the Emacs
repository. It was only a proof of concept and there was never any interest
expressed in it. I wanted to remove it now to avoid confusion in the future.
Anyone wishing to just debug with GDB in Emacs would do best to use the mode
that comes with his/her version of Emacs.
--
Nick http://users.snap.net.nz/~nickrob
prev parent reply other threads:[~2009-09-25 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 23:13 Nick Roberts
2009-09-25 1:40 ` Joel Brobecker
2009-09-25 2:00 ` Nick Roberts
2009-09-25 8:49 ` Eli Zaretskii
2009-09-25 11:02 ` Nick Roberts [this message]
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=19132.41804.225362.342372@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--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