From: nickrob@snap.net.nz (Nick Roberts)
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Restore GDB/MI fuctionality removed by r99212
Date: Mon, 29 Mar 2010 10:52:18 +1300 [thread overview]
Message-ID: <19375.53138.346849.753634@totara.tehura.co.nz> (raw)
In-Reply-To: <83iq8g39lj.fsf@gnu.org>
> This change:
>
> revno: 99756
> committer: Nick Roberts <nickrob@snap.net.nz>
> branch nick: trunk
> timestamp: Sun 2010-03-28 02:27:43 +1300
> message:
> Restore GDB/MI fuctionality removed by r99212:
>
> added:
> lisp/progmodes/gdb-mi.el
> removed:
> lisp/progmodes/gdb-ui.el
> modified:
> doc/emacs/building.texi
> doc/emacs/emacs.texi
> etc/NEWS
> lisp/Makefile.in
> lisp/progmodes/gud.el
>
> has no entries in the pertinent ChangeLog files. I think it should
> have them.
That's because you can get this changeset information from "bzr log -v". which
includes the names of all files that have been committed (actually there is
one ChangeLog entry in the parent directory). I think he ChangeLog file is a
throwback to CVS file based commits. We seem to get all the headaches of Bzr
and none of the benefits. It's probably been discussed before but ISTR at
that time RMS appeared to think that "bzr log" required a remote connection
when, in reality, it just retrieves information locally. I don't want to
campaign for this, so if people still want ChangeLog files I will add the
entries.
> Also, I think ldefs-boot.el should be updated as well, as it now has
> references to gdb-ui.el that is no longer in the tree.
OK thanks, I didn't realise that. I've updated this file now (this one
doesn't appear to get a ChangeLog entry.
--
Nick http://users.snap.net.nz/~nickrob
next prev parent reply other threads:[~2010-03-28 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 12:38 Restore GDB/MI fuctionality removed by r99212 Eli Zaretskii
2010-03-28 21:52 ` Nick Roberts [this message]
2010-03-28 23:34 ` Stefan Monnier
2010-03-30 0:39 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19375.53138.346849.753634@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).