Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: David Daney <ddaney@caviumnetworks.com>, gdb@sourceware.org
Subject: Re: Discussing the next GDB release (GDB 7.0?)
Date: Thu, 15 Jan 2009 23:54:00 -0000	[thread overview]
Message-ID: <daef60380901151553n3d26f73cjc3ff48f980c8d2a7@mail.gmail.com> (raw)
In-Reply-To: <20090115173646.GC31296@adacore.com>

Hi Joel,

Do we need process record and replay in 7.0 release?
It's in submit process.

Thanks,
Hui

On Fri, Jan 16, 2009 at 01:36, Joel Brobecker <brobecker@adacore.com> wrote:
>
> > Acknowledging that these things can change, do you have a tentative
> > release date in mind?
>
> Not yet, no - this will depend on how fast the Python gurus think
> they can get the Python included. I don't want to push them, though.
>
> > Hardware watch support for mips{,el,64,64el}-linux.  The kernel support
> > is in as of 2.6.28, but my gdb patches need a little work.  I will try
> > to have them ready soon.
>
> OK. I won't add it to our list, as I don't think this is blocking
> for the release. Just cleanup and submit quickly, and then hassle us
> to review the patches, ok?
>
> --
> Joel


  reply	other threads:[~2009-01-15 23:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  3:46 Joel Brobecker
2009-01-15  4:18 ` Eli Zaretskii
2009-01-15 10:43 ` Vladimir Prus
2009-01-15 17:12 ` Joel Brobecker
2009-01-15 17:17 ` Tom Tromey
2009-01-15 17:24   ` Daniel Jacobowitz
2009-01-15 17:31     ` Joel Brobecker
2009-01-28  3:49   ` Thiago Jung Bauermann
2009-01-30  0:43     ` Joel Brobecker
2009-02-02 13:48       ` Thiago Jung Bauermann
2009-02-04 19:17   ` Tom Tromey
2009-02-06  0:48     ` Joel Brobecker
2009-01-15 17:24 ` David Daney
2009-01-15 17:37   ` Joel Brobecker
2009-01-15 23:54     ` teawater [this message]
2009-01-16  2:29       ` teawater
2009-01-16  3:40         ` Joel Brobecker
2009-01-16  6:32           ` teawater
2009-01-16 16:24             ` Tom Tromey
2009-01-16 14:30           ` Marc Khouzam
2009-01-20 18:25             ` Jakob Engblom
2009-01-21  0:18               ` teawater
2009-01-21  3:16                 ` teawater
2009-01-27  5:09               ` Michael Snyder
2009-01-27  5:01             ` Michael Snyder
2009-01-30  0:48               ` Joel Brobecker
2009-01-16  3:47 ` Joel Brobecker
2009-01-16  5:48   ` Paul Pluzhnikov
2009-01-16  8:46     ` Eli Zaretskii
2009-01-16 14:55   ` Daniel Jacobowitz
2009-01-16 14:30 ` Joel Sherrill
2009-01-17  3:09   ` Joel Brobecker
2009-01-20  8:09 ` Nathan Sidwell
2009-01-20 10:41   ` Joel Brobecker
2009-01-20 11:25     ` Nathan Sidwell

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=daef60380901151553n3d26f73cjc3ff48f980c8d2a7@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=gdb@sourceware.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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox