From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: gdb@sourceware.org
Subject: Re: time to create the gdb-7.0.1 release (?)
Date: Fri, 18 Dec 2009 07:44:00 -0000 [thread overview]
Message-ID: <4B2B32D5.10204@rtems.org> (raw)
In-Reply-To: <20091218061736.GV2804@adacore.com>
On 12/18/2009 07:17 AM, Joel Brobecker wrote:
> Hello,
>
> According to our suggested schedule, yesterday (Dec 17) was the time
> we were hoping to produce gdb-7.0.1. Looking at the ChangeLog, here
> is the list of changes:
> Anything else that should go in that (corrective) release?
Wasn't there a "shipping wrong COPYING" (GPLv3 / GPLv2) issue?
Ralf
next prev parent reply other threads:[~2009-12-18 7:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 6:17 Joel Brobecker
2009-12-18 7:44 ` Ralf Corsepius [this message]
2009-12-18 8:10 ` Joel Brobecker
2009-12-18 8:52 ` Hui Zhu
2009-12-18 8:56 ` Joel Brobecker
2009-12-18 9:02 ` Hui Zhu
2009-12-18 9:45 ` Joel Brobecker
2009-12-18 14:24 ` Jack Howarth
2009-12-18 14:33 ` Joel Brobecker
2009-12-18 17:35 ` Michael Snyder
2009-12-18 17:40 ` Joel Brobecker
2009-12-18 17:54 ` Michael Snyder
2009-12-19 18:03 ` Jan Kratochvil
2009-12-21 6:01 ` Joel Brobecker
2009-12-21 9:07 ` Jan Kratochvil
2009-12-20 20:27 ` Jan Kratochvil
2009-12-21 9:54 ` 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=4B2B32D5.10204@rtems.org \
--to=ralf.corsepius@rtems.org \
--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