From: Nathan Sidwell <nathan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org, Pedro Alves <pedro@codesourcery.com>
Subject: Re: Discussing the next GDB release (GDB 7.0?)
Date: Tue, 20 Jan 2009 11:25:00 -0000 [thread overview]
Message-ID: <4975B4A9.1090808@codesourcery.com> (raw)
In-Reply-To: <20090120104135.GL5709@adacore.com>
Joel Brobecker wrote:
>> What about merging the multiprocess bits from the multiprocess branch?
>> If we're going for a major version increment, might as well have as
>> many new features as possible :)
>
> That's an interesting feature to have - I would love to have it, as
> any new feature, but can this be pushed to trunk in a reasonable
> amount of time? Otherwise, the question becomes: Do we want to delay
> the release for this feature? What are the limitations in the current
> implementation?
Pedro has a much better handle on the state of that branch than me.
> Right now, I am guestimating we're two to three months away from branching.
> I need to discuss this delay with the Python guys too...
I planned to have CodeSourcery work on getting that branch merged by the end of
April. Hitting the beginning of April is probably too soon.
Please let me know if there's more we can do to get multi-process into GDB 7
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery
prev parent reply other threads:[~2009-01-20 11:25 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
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 [this message]
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=4975B4A9.1090808@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pedro@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