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: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, <gdb-patches at sourceware dot org>
- Date: Tue, 3 May 2016 11:01:43 -0400
- Subject: Re: gdb-7.11.1 re-spin update
- Authentication-results: sourceware.org; auth=none
- References: <20160425214951 dot GA4079 at adacore dot com> <5728B36D dot 6090304 at ericsson dot com> <alpine dot DEB dot 2 dot 20 dot 1605031428040 dot 7094 at digraph dot polyomino dot org dot uk>
On 16-05-03 10:30 AM, Joseph Myers wrote:
> On Tue, 3 May 2016, Simon Marchi wrote:
>
>> I think that this particular problem could be efficiently solved with scripting.
>> Apparently, Bugzilla now has an API [1], although I can't find how to use it on
>> the sourceware BZ, maybe it's too old.
>>
>> If that API was accessible, it should be easy to write a script that prints a
>> nicely formatted list of all issues with target milestone == 7.11.1, ready to
>> copy paste in the email. It could also tell which issues are still open and warn
>> if any of these doesn't have an assignee. So it could give you a quick overview
>> of the state of the release.
>
> The REST API definitely works for sourceware Bugzilla; we use it for glibc
> to generate a list of fixed bugs for the NEWS file.
>
> https://sourceware.org/git/?p=glibc.git;a=blob;f=scripts/list-fixed-bugs.py;h=51f3c36e693a67978ba58706499db132fefe1e4e;hb=HEAD
Thanks, I'll have a look!
Just glancing at it quickly, it very much looks like what I was describing :).