This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: gdb-7.11.1 re-spin update
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 2 May 2016 12:38:04 -0700
- Subject: Re: gdb-7.11.1 re-spin update
- Authentication-results: sourceware.org; auth=none
- References: <20160425214951 dot GA4079 at adacore dot com> <571F5BF8 dot 4090205 at redhat dot com> <20160502154642 dot GA4771 at adacore dot com> <7290d675-bb3c-fa59-2021-7ab59657cb3f at redhat dot 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