From: Tom Tromey <tromey@adacore.com>
To: overseers@sourceware.org
Subject: buglet in commit -> bugzilla script
Date: Thu, 08 Oct 2020 10:14:48 -0600 [thread overview]
Message-ID: <87k0w0k83r.fsf@tromey.com> (raw)
I found a buglet in the script that examines commit messages and then
updates bugzilla.
This gdb commit:
commit d706b69e48268ccf3e95fd29b5374ac94c3a507b
Author: Tom Tromey <tromey@adacore.com>
Date: Tue Sep 8 10:20:44 2020 -0600
mentions a PR:
PR win32/25302 notes that gdb will crash when trying to "run" even a
simple program on Windows. The essential bug here is that the BFD
cache can easily be corrupted -- I have sent a separate patch for
that.
However it did not end up here:
https://sourceware.org/bugzilla/show_bug.cgi?id=25302
I think the reason is that the PR-matching regexp doesn't include "0-9",
so it doesn't realize that "win32" is a component name.
Could someone please fix this?
thanks,
Tom
reply other threads:[~2020-10-08 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87k0w0k83r.fsf@tromey.com \
--to=tromey@adacore.com \
--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).