Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, GDB Development <gdb@sourceware.org>
Subject: Re: ambiguous linespec decision point
Date: Thu, 01 Dec 2011 17:10:00 -0000	[thread overview]
Message-ID: <m3borscj5f.fsf@redhat.com> (raw)
In-Reply-To: <m3mxbdjj8s.fsf@redhat.com> (Sergio Durigan Junior's message of	"Wed, 30 Nov 2011 21:14:27 -0200")

Sergio Durigan Junior <sergiodj@redhat.com> writes:

> Tom Tromey <tromey@redhat.com> writes:
>
>> It is time to decide whether the ambiguous linespec patch should go in
>> for 7.4 or be delayed until 7.5.  Since I am ready to be done with this
>> patch, I don't think I can be really objective about it, so I am looking
>> for input on this topic.
>>
>> At this point the patch is regression free, according to the test suite,
>> and Joel has fixed the remaining problems shown by the AdaCore test
>> suite.
>>
>> The main risk is just that the patch is quite large and so there may be
>> regressions lurking that the test suite has not revealed.
>
> I know my opinion does not count that much, but I think it is OK to
> check it in since you both spent quite some time hunting and solving
> bugs on this.  Moreover, after the branching we would have two weeks
> IIRC to find some regression and fix it.

I agree with Sergio, and even if the test period goes on a week or two
more, the value this patch would bring is great.

Cheers,

Phil


  parent reply	other threads:[~2011-12-01 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 17:10 Tom Tromey
2011-11-30 23:15 ` Sergio Durigan Junior
2011-11-30 23:31   ` Joel Brobecker
2011-12-01 17:10   ` Phil Muldoon [this message]
2011-12-01 13:04 ` Gary Benson
2011-12-01 16:55   ` Joel Brobecker
2011-12-01 21:52 ` Tom Tromey

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=m3borscj5f.fsf@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=sergiodj@redhat.com \
    --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