From: "Martin Liška" <mliska@suse.cz>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC bugzilla: REST API
Date: Thu, 12 Mar 2020 09:27:12 +0100 [thread overview]
Message-ID: <e92a4a1f-5b2f-1dd8-a551-a146b0845d86@suse.cz> (raw)
In-Reply-To: <20200311231533.GA79103@elastic.org>
On 3/12/20 12:15 AM, Frank Ch. Eigler wrote:
> Hi -
>
>> I'm working on a script that will catch the missing email into
>> Bugzilla that are triggered by git commits mentioning a PR.
>> For that I would need the enablement of REST API that was enabled
>> in previous bugzilla instance.
>
> I believe this should work now. Thanks to Joseph Myers for
> pointing out that we were missing some more perl modules.
> Fought with koji & etc. awhile and now bugzilla's checksetup.pl
> is happy all around.
Hello.
Thank you for that. I can confirm it works fine now.
Martin
>
> - FChE
>
prev parent reply other threads:[~2020-03-12 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 10:22 Martin Liška
2020-03-11 18:41 ` Frank Ch. Eigler
2020-03-11 21:17 ` Joseph Myers
2020-03-11 23:15 ` Frank Ch. Eigler
2020-03-12 8:27 ` Martin Liška [this message]
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=e92a4a1f-5b2f-1dd8-a551-a146b0845d86@suse.cz \
--to=mliska@suse.cz \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).