This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: status update for GDB 7.7?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, Philippe Waroquiers <philippe dot waroquiers at skynet dot be>, Doug Evans <dje at google dot com>
- Date: Mon, 2 Dec 2013 11:49:20 +0400
- Subject: Re: status update for GDB 7.7?
- Authentication-results: sourceware.org; auth=none
- References: <20131202035637 dot GQ3114 at adacore dot com> <20131202073623 dot GA13911 at host2 dot jankratochvil dot net>
> It is not checked in. The patch is IMO done in the link above.
>
> Just Doug required some whole new feature/patchset just because of the
> testcase there and currently I work on other more urgent things:
> https://sourceware.org/ml/gdb-patches/2013-10/msg00287.html
OK. So what do you guys want to do with respect to the release?
Some possible options:
(1) Defer the patch for the next release, hoping there will be
more time to look into the new ideas?
(2) Or defer the release while waiting for someone to find that
time?
(3) Commit the patch as is, and defer the new improvement for
later?
Any other suggestions? From my vantage point, it sounds like we have
let, in this thread, best be the enemy of good. IIUC, the patch is
OK, but blocked because we could do better in the testcase? Or did
a small issue in the testcase raise a bigger issue?
--
Joel