From: Joseph Myers <joseph@codesourcery.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Joel Brobecker <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Subject: Re: gdb-7.11.1 re-spin update
Date: Tue, 03 May 2016 14:31:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1605031428040.7094@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5728B36D.6090304@ericsson.com>
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
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-05-03 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 21:50 Joel Brobecker
2016-04-26 12:16 ` Pedro Alves
2016-05-02 15:46 ` Joel Brobecker
2016-05-02 17:23 ` Pedro Alves
2016-05-02 19:38 ` Joel Brobecker
2016-05-02 19:41 ` Pedro Alves
2016-05-02 21:16 ` Joel Brobecker
2016-05-02 21:30 ` Pedro Alves
2016-05-05 13:49 ` Joel Brobecker
2016-04-27 19:36 ` Jan Kratochvil
2016-05-03 14:19 ` Simon Marchi
2016-05-03 14:31 ` Joseph Myers [this message]
2016-05-03 15:01 ` Simon Marchi
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=alpine.DEB.2.20.1605031428040.7094@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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