From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: Our next GDB release (GDB version 6.8)
Date: Thu, 31 Jan 2008 08:15:00 -0000 [thread overview]
Message-ID: <fns00u$eg0$1@ger.gmane.org> (raw)
In-Reply-To: <20080126005319.GD21874@adacore.com>
Joel Brobecker wrote:
> Hello GDB enthusiasts!
>
> The schedule on the GDB website shows that we were planning on
> making a new GDB release (GDB version 6.8) soon: Branch creation
> on Feb 5th, and a then an official release a month later.
> Looks like it's going to be tight to make these dates, but
> I don't think it's a problem.
>
> I would like us to start drawing a list of things that we'd like
> to include in that release. For one, I'd like to list the changes
> I submitted regarding Ada support, at least the ones that provide
> the most value. Maybe I'll also find some time to work on something
> we briefly discussed a few years back regarding the README file, and
> maybe think about the NEWS file too. That's not critical though,
> just making the release slightly more labor intensive.
>
> I propose we use a wiki page again. In fact, I was surprised to
> see that someone already created one. Should I thank Nick for that?
>
> Opinions? Items that should be put on the list of things to finish
> for the release? Please send them here and I'll add them to the
> wiki. If a thread was already started, please post a link to it
> as well.
I would like these two patches to go in:
http://sourceware.org/ml/gdb-patches/2008-01/msg00629.html
http://sourceware.org/ml/gdb-patches/2008-01/msg00632.html
They, together, fix a bug where gdb produces a totally bogus MI
response.
- Volodya
next prev parent reply other threads:[~2008-01-31 8:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 0:53 Joel Brobecker
2008-01-26 9:21 ` Eli Zaretskii
2008-01-26 13:59 ` Joel Brobecker
2008-01-26 14:14 ` Eli Zaretskii
2008-01-26 16:07 ` Joel Brobecker
2008-01-26 16:36 ` Eli Zaretskii
2008-01-26 17:00 ` Christopher Faylor
2008-01-26 17:19 ` Eli Zaretskii
2008-01-26 17:25 ` Joel Brobecker
2008-01-26 17:19 ` Joel Brobecker
2008-01-27 7:32 ` Nicholas Mc Guire
2008-01-27 15:10 ` Daniel Jacobowitz
[not found] ` <Pine.LNX.4.58.0801282316360.2555@vlab.hofr.at>
2008-01-29 13:50 ` Daniel Jacobowitz
2008-01-29 20:23 ` Eli Zaretskii
2008-01-27 17:05 ` Jim Blandy
2008-01-28 10:56 ` Pierre Muller
2008-01-28 12:35 ` Pedro Alves
2008-01-28 12:41 ` Pedro Alves
2008-01-28 17:40 ` Paul Koning
2008-01-31 14:49 ` Pedro Alves
2008-01-28 21:02 ` Thiago Jung Bauermann
2008-01-29 21:19 ` Joel Brobecker
2008-01-30 10:57 ` Markus Deuling
2008-01-30 18:32 ` Joel Brobecker
2008-01-30 23:14 ` Doug Evans
2008-01-31 0:09 ` Joel Brobecker
2008-01-31 8:15 ` Vladimir Prus [this message]
2008-01-31 16:55 ` Joel Brobecker
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='fns00u$eg0$1@ger.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb@sources.redhat.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