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>, gdb-patches@sources.redhat.com
Subject: Re: MI: Another -var-update bug? [PATCH]
Date: Mon, 01 Jan 2007 16:24:00 -0000	[thread overview]
Message-ID: <20070101162437.GA13674@nevyn.them.org> (raw)
In-Reply-To: <20061231021947.GA719@nevyn.them.org>

On Sat, Dec 30, 2006 at 09:19:47PM -0500, Daniel Jacobowitz wrote:
> > I can't speak for others but in Emacs I just use a grey font for variables that
> > go out of scope and leave it to the user to explicily delete them.  The worst
> > scenario, if there is a problem at all, is that the watch expression would be
> > inexplicably greyed for one step.
> 
> Good, that's not bad at all.  If Vlad doesn't think this is likely to
> break kdevelop or Eclipse, the patch is OK.

So, given that, why did you commit it?  Maybe Vlad agreed with the
patch in another thread that I didn't read?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-01-01 16:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 11:09 MI: Another -var-update bug? Nick Roberts
2006-12-13  6:32 ` MI: Another -var-update bug? [PATCH] Nick Roberts
2006-12-30 15:06   ` Daniel Jacobowitz
2006-12-30 22:43     ` Nick Roberts
2006-12-31  2:19       ` Daniel Jacobowitz
2007-01-01 16:24         ` Daniel Jacobowitz [this message]
2007-01-01 22:13           ` Nick Roberts
2007-01-04 18:51             ` Vladimir Prus
2007-01-04 19:43               ` Nick Roberts
2007-01-04 18:49   ` Vladimir Prus
2007-01-04 23:59     ` Nick Roberts
2007-01-05  9:10       ` Vladimir Prus
2007-01-05 15:10         ` Daniel Jacobowitz

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=20070101162437.GA13674@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