public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
		gdb-patches <gdb-patches@sourceware.org>
Subject: Re: 3 weeks to GDB 7.9.1 release?
Date: Sat, 02 May 2015 15:33:00 -0000	[thread overview]
Message-ID: <CADPb22RtHkDUw284K2CdwqUi51E3a6+aS9nJnVJhYZjXY_wQxg@mail.gmail.com> (raw)
In-Reply-To: <20150422171434.GL4764@adacore.com>

On Wed, Apr 22, 2015 at 10:14 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>>   Would the patch to gdb/p-exp.y that fixes issue PR 127815
>> https://sourceware.org/bugzilla/show_bug.cgi?id=17815
>>
>> be acceptable without the testsuite change?
>>
>>   This patch was accepted recently by Doug, and committed to trunk.
>> https://sourceware.org/ml/gdb-patches/2015-04/msg00735.html
>>
>> The patch [part 1/3] itself is at:
>> https://sourceware.org/ml/gdb-patches/2015-02/msg00111.html
>>
>> Or would the application of the three parts of the patch be more acceptable?
>> The two other parts are at:
>> https://sourceware.org/ml/gdb-patches/2015-02/msg00112.html
>> and
>> https://sourceware.org/ml/gdb-patches/2015-02/msg00113.html
>
> It's mostly your's and Doug's decision. The general idea is to
> only take patches that are safe and fix an important issue. But
> if it's only affecting Pascal, then we can be a little more
> relaxed about it.

Agreed.
I think this and the tests can go into the branch.

> Regarding the testsuite patches, since they cannot harm the debugger,
> they should be part of the set being considered for inclusion in
> the gdb-7.9-branch.
>
> If the decision is to include the patch, please remember to update
> the wiki page as well!
>
> --
> Joel

  reply	other threads:[~2015-05-02 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 13:32 Joel Brobecker
2015-04-22 13:59 ` Eli Zaretskii
2015-04-22 14:31   ` Joel Brobecker
2015-04-22 14:38     ` Eli Zaretskii
2015-04-22 15:22 ` Pierre Muller
2015-04-22 17:14   ` Joel Brobecker
2015-05-02 15:33     ` Doug Evans [this message]
2015-05-02 22:46       ` Pierre Muller
2015-05-04 12:12         ` Joel Brobecker
2015-05-01 22:23 ` Sergio Durigan Junior
2015-05-02 15:29   ` Doug Evans
2015-05-06 13:42 ` 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=CADPb22RtHkDUw284K2CdwqUi51E3a6+aS9nJnVJhYZjXY_wQxg@mail.gmail.com \
    --to=dje@google.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).