Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org,
	Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	Doug Evans <dje@google.com>
Subject: Re: status update for GDB 7.7?
Date: Mon, 02 Dec 2013 07:49:00 -0000	[thread overview]
Message-ID: <20131202074920.GT3114@adacore.com> (raw)
In-Reply-To: <20131202073623.GA13911@host2.jankratochvil.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


  reply	other threads:[~2013-12-02  7:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02  3:56 Joel Brobecker
2013-12-02  7:36 ` Jan Kratochvil
2013-12-02  7:49   ` Joel Brobecker [this message]
2013-12-02  8:02     ` Jan Kratochvil
2013-12-02 10:35       ` Joel Brobecker
2013-12-02 19:43   ` Doug Evans
2013-12-02 21:28     ` Jan Kratochvil
2013-12-03  2:53       ` Joel Brobecker
2013-12-03 19:22 ` Philippe Waroquiers
2013-12-04 16:58   ` 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=20131202074920.GT3114@adacore.com \
    --to=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=philippe.waroquiers@skynet.be \
    /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