From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: 2 weeks away from potential GDB 7.4.1 release...
Date: Thu, 12 Apr 2012 17:34:00 -0000 [thread overview]
Message-ID: <201204121334.54411.vapier@gentoo.org> (raw)
In-Reply-To: <20120412153301.GW25623@adacore.com>
[-- Attachment #1: Type: Text/Plain, Size: 777 bytes --]
On Thursday 12 April 2012 11:33:01 Joel Brobecker wrote:
> It's been almost 3 months since the 7.4 release, and it's time to think
> about whether we want to make a corrective release or not. The tentative
> date is Apr 23rd. We have a few changes already in the branch, are the
> problems serious enough to warrant a release? Any other changes that
> should go in the 7.4 branch (please, only refer to very very safe fixes,
> or fixes to critical bugs)?
there's a sim patch i think would be useful on the branch (fixes a build issue
reported by someone shortly after the 7.4 release). i haven't committed to a
branch on sourceware.org before, so is there anything i should be aware of ?
a quick search on the gdb site didn't seem to turn up anything.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-12 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 15:33 Joel Brobecker
2012-04-12 16:28 ` Paul Smith
2012-04-12 17:18 ` Joel Brobecker
2012-04-12 18:04 ` Paul Smith
2012-04-12 19:14 ` Joel Brobecker
2012-04-13 13:11 ` Jan Kratochvil
2012-04-12 17:34 ` Mike Frysinger [this message]
2012-04-12 17:42 ` Joel Brobecker
2012-04-13 8:07 ` Pierre Muller
2012-04-13 13:16 ` Jan Kratochvil
2012-04-13 19:10 ` Joel Brobecker
2012-04-19 15:29 ` Joel Brobecker
2012-04-20 8:44 ` Jan Kratochvil
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=201204121334.54411.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.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