RE: 3 weeks to GDB 7.9.1 release?

["Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>]

  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


  I would really like to have it in 7.9.1
as it is completely pascal language specific.

Pierre Muller
as pascal language maintainer

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : mercredi 22 avril 2015 15:33
> À : gdb-patches@sourceware.org
> Objet : 3 weeks to GDB 7.9.1 release?
> 
> Hello everyone,
> 
> Planned date for 7.9.1 re-spin is Wed May, 13th. It appears that
> it's been a fairly smooth sailing for the gdb-7.9-branch since
> GDB 7.9 was released... Our release wiki page
> (https://sourceware.org/gdb/wiki/GDB_7.9_Release) shows that only
> one issue was fixed, and we only have 1 that has been identified
> as blocking:
> 
>    [Doug?] PR18066 argument "word" seems broken in Command.complete
>    (text, word)
> 
> Anything else that should be seen as blocking for 7.9.1?
> 
> This is a good opportunity to remind everyone that patches to
> release branches, once the first official release has been made,
> must be documented on that page. Otherwise, I will not be able
> to provide the full list of improvements that this release brings.
> I reviewed the commits on that branch, and identified 2 patches that
> have been pushed without following the full procedure, and I will be
> emailing those authors privately.  But the branch is polluted by
> a number of date-update commits, so if you know you've made a change
> and forgot to follow the procedure, it's not too late: You need a PR,
> which you can create if you don't have one already, and then just add
> a one-line description to the wiki page shown above (that description
> can simply be the subject line of the PR).
> 
> Thank you,
> --
> Joel