Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH: gdb/mi] gdb-mi.el
Date: Sat, 30 Apr 2005 19:53:00 -0000	[thread overview]
Message-ID: <20050430195303.GC6713@nevyn.them.org> (raw)
In-Reply-To: <16955.41571.706228.362525@farnswood.snap.net.nz>

On Sat, Mar 19, 2005 at 04:54:11PM +1300, Nick Roberts wrote:
> Nick Roberts (2 Mar 2005) writes:
> 
>  > This patch updates gdb-mi.el so that it works again with Emacs in the CVS
>  > repository at Savannah (Emacs 22.0.50) which, hopefully, will be released,
>  > one day, as Emacs 22. I plan to update this file to reflect the current and
>  > future changes I make for MI in GDB. The slow release cycle of Emacs makes
>  > it impossible to track these changes from the Emacs side.
>  > 
>  > Nick
>  > 
>  > Comment from gdb-mi.el:
>  > ;; This file uses GDB/MI as the primary interface to GDB. It is still under
>  > ;; development and is part of a process to migrate Emacs from annotations
>  > ;; (as used in gdb-ui.el) to GDB/MI.
> 
> I've updated this patch to include the new option to the MI command,
> -var-update, that I've described in my previous post.
> 
> As this file is separate code, it can't break GDB. Could a global maintainer
> please authorise this commit.

Could you please include a ChangeLog entry for the pdate?

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-30 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  8:18 Nick Roberts
2005-03-19  3:56 ` Nick Roberts
2005-04-30 19:53   ` Daniel Jacobowitz [this message]
2005-05-01  8:12     ` Nick Roberts
2005-05-01 15:02       ` Daniel Jacobowitz
2005-05-02  4:38         ` 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=20050430195303.GC6713@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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