Re: gdb-7.11.1 re-spin update

[Joel Brobecker <brobecker@adacore.com>]

> What I do, is subscribe to the gdb-prs mailing list:
> 
>  https://sourceware.org/ml/gdb-prs/
> 
> so I get a message for _every_ change done on our bugzilla.

I could do that, and filter on any of:

    X-Bugzilla-Changed-Fields: cc target_milestone
    X-Bugzilla-Target-Milestone:

The summary provides the assignee, so I think I think we can try that
for this release. If it works well, I suggest we completely switch
over to a bugzilla-only approach starting with the following release.

It looks like https://sourceware.org/bugzilla/show_bug.cgi?id=20029
had its target milestone set to 7.11.1 by the reporter (nightstrike).
That's one of the things I'd like to catch, just to make sure things
get discussed.  It should be fairly easy to fix that one, especiallyi
you posted a link to a patch pending review. But if the patch doesn't
make it, I think we can release without it, since warnings on the branch
are not fatal.

-- 
Joel