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: Vladimir Prus <vladimir@codesourcery.com>,
		gdb-patches@sources.redhat.com
Subject: Re: MI: frozen variable objects
Date: Fri, 17 Nov 2006 15:19:00 -0000	[thread overview]
Message-ID: <20061117151857.GB31319@nevyn.them.org> (raw)
In-Reply-To: <17756.60994.909354.46765@kahikatea.snap.net.nz>

On Fri, Nov 17, 2006 at 12:03:30PM +1300, Nick Roberts wrote:
> > I'm not particularly inclined to wait, since none of this will show up
> > unless your target / IDE specifically try to use it, but I'm sure I
> > could be persuaded.
> 
> If existing behaviour is broken it _should_ show up.  A six month release cycle
> doesn't seem long to wait especially coming from Emacs whose last mainline
> release was Oct 2001 (GDB 5.3 was current when I started!).  Maybe there is
> another agenda with Emacs, I don't know, but presumably it will be released one
> day and I would like it to work with current GDB when it is.

I think Vladimir's said everything I would have said in response to
this.  Is your concern breaking your MI frontend in Emacs?  If so,
then you need to test - either routinely on HEAD, or if you have
more limited time, then on release branches.  That's why we keep
release branches around for a few weeks and announce prereleases.

Whether the patch lands on GDB 6.6 or 6.7 doesn't make much difference
to the risk.  If there's no testing, it might be released broken; if
there is testing, it won't be.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-11-17 15:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 21:53 Nick Roberts
2006-11-16 22:00 ` Daniel Jacobowitz
2006-11-16 23:07   ` Nick Roberts
2006-11-17 15:19     ` Daniel Jacobowitz [this message]
2006-11-17 20:52       ` Nick Roberts
2006-11-17 21:05         ` Daniel Jacobowitz
2006-11-17 23:12           ` Nick Roberts
2006-11-18 11:00           ` Eli Zaretskii
2006-11-17  6:25 ` Vladimir Prus
2006-11-17 18:14 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-11-18  6:59 Nick Roberts
2006-11-16 12:48 Vladimir Prus
2006-11-16 13:58 ` Greg Watson
2006-11-16 15:25   ` Frederic RISS
2006-11-16 15:55     ` Daniel Jacobowitz
2006-11-16 16:26       ` Frederic RISS
2006-11-16 16:34         ` Daniel Jacobowitz
2006-11-17 15:21       ` Greg Watson
2006-11-16 18:55     ` Vladimir Prus
2006-11-16 21:36       ` Frédéric Riss
2006-11-17  6:17         ` Vladimir Prus
2006-11-17  8:54           ` Frederic RISS
2006-11-16 18:47   ` Vladimir Prus
2006-11-17 15:09     ` Greg Watson
2006-11-17 15:15       ` Daniel Jacobowitz
2006-11-17 15:26         ` Greg Watson
2006-11-17 15:33           ` Daniel Jacobowitz
2006-11-17 15:41             ` Greg Watson
2006-11-17 15:45               ` Daniel Jacobowitz
2006-11-17 18:16               ` Daniel Jacobowitz
2006-11-17 15:35         ` Greg Watson
2006-11-17 15:27       ` Vladimir Prus

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=20061117151857.GB31319@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    --cc=vladimir@codesourcery.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