From: Joel Brobecker <brobecker@adacore.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 7.1 release planning...
Date: Fri, 08 Jan 2010 11:08:00 -0000 [thread overview]
Message-ID: <20100108110816.GN4623@adacore.com> (raw)
In-Reply-To: <B0E22CC9-9C19-479E-8720-E03F598FB15B@adacore.com>
> I'd like to improve the behaviour on Darwin. Most of the work has
> already been integrated and I think the last submitted patch would go
> in before the dead-line.
This makes sense to me. Can you add a reference to the patches currently
outstanding in the gdb-7.0 release page (wiki)? Or, if you prefer, you
can send the URLs to me, and I'll update the page.
> The last known issue is proper handling of common symbols, but this
> work is not yet ready. I will see if I can submit this before Jan
> 15th.
OK. If you manage to make a change that only influences Darwin,
and you think the patch is safe enough, you can elect to put it
in the branch as well (your decision as the Darwin maintainer).
--
Joel
next prev parent reply other threads:[~2010-01-08 11:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 4:21 Joel Brobecker
2010-01-08 9:24 ` Tristan Gingold
2010-01-08 11:08 ` Joel Brobecker [this message]
2010-01-08 13:49 ` Jan Kratochvil
2010-01-08 18:44 ` Michael Snyder
2010-01-09 3:08 ` Joel Brobecker
2010-01-08 13:53 ` Daniel Jacobowitz
2010-01-08 16:14 ` Tom Tromey
2010-01-09 3:18 ` Joel Brobecker
2010-01-11 19:58 ` Tom Tromey
2010-01-14 4:54 ` Joel Brobecker
2010-01-08 19:28 ` Stan Shebs
2010-01-08 22:32 ` Pedro Alves
2010-01-08 23:46 ` Stan Shebs
2010-01-09 3:31 ` Joel Brobecker
2010-01-09 16:52 ` Marc Khouzam
2010-01-11 9:48 ` Joel Brobecker
2010-01-11 14:31 ` Pedro Alves
2010-01-11 14:36 ` Pedro Alves
2010-01-13 23:17 ` Michael Snyder
2010-01-14 3:30 ` 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=20100108110816.GN4623@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.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