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: Sun, 01 May 2005 15:02:00 -0000 [thread overview]
Message-ID: <20050501150224.GA970@nevyn.them.org> (raw)
In-Reply-To: <17012.36714.197045.790859@farnswood.snap.net.nz>
On Sun, May 01, 2005 at 08:12:26PM +1200, Nick Roberts wrote:
> > Could you please include a ChangeLog entry for the pdate?
>
> 2005-05-01 Nick Roberts <nickrob@snap.net.nz>
>
> * mi/gdb-mi.el: Update for changes in Emacs 22.0.50.
> Use "-var-update --with-values" for faster re-display of
> watch expressions.
>
> Please note that I have submitted a patch for "-var-update --with-values"
> which is also waiting approval.
The last message in the thread was comments from Bob. Are you going to
respond to them, or would you rather I review it first?
Does this patch require that one?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-01 15:02 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
2005-05-01 8:12 ` Nick Roberts
2005-05-01 15:02 ` Daniel Jacobowitz [this message]
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=20050501150224.GA970@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