From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb-7.5 branch ready for first release?
Date: Thu, 16 Aug 2012 22:36:00 -0000 [thread overview]
Message-ID: <20120816223625.GB2798@adacore.com> (raw)
In-Reply-To: <87mx1umv8m.fsf@fleche.redhat.com>
> Joel> Looks a little tricky, and MarkK expressed some reservations on
> Joel> the approach. I suggest we keep this one out of 7.5?
>
> FWIW I already put it on the branch.
Ha! That makes it simpler :).
> However, this patch doesn't affect that design one way or another.
> Instead it fixes a concrete bug in the code. It does so in a way that,
> I believe, is safe and relatively clear.
Works for me. I'll try making the release tomorrow.
Thanks, Tom.
--
Joel
next prev parent reply other threads:[~2012-08-16 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 13:45 Joel Brobecker
2012-08-03 17:43 ` Tom Tromey
2012-08-06 1:42 ` Joel Brobecker
2012-08-06 8:28 ` Jan Kratochvil
2012-08-06 13:12 ` Joel Brobecker
2012-08-06 14:35 ` Luis Gustavo
2012-08-16 20:07 ` Joel Brobecker
2012-08-16 20:34 ` Tom Tromey
2012-08-16 22:36 ` Joel Brobecker [this message]
2012-08-06 19:38 ` Ralf Corsepius
2012-08-08 20:47 ` Tom Tromey
2012-08-09 4:44 ` Ralf Corsepius
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=20120816223625.GB2798@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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