From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30029] New: Please patch email-to-bugzilla to recognize Bug: trailer
Date: Fri, 20 Jan 2023 16:29:15 +0000 [thread overview]
Message-ID: <bug-30029-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30029
Bug ID: 30029
Summary: Please patch email-to-bugzilla to recognize Bug:
trailer
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: tromey at sourceware dot org
Target Milestone: ---
Created attachment 14610
--> https://sourceware.org/bugzilla/attachment.cgi?id=14610&action=edit
the patch
In gdb, we've starting using a Bug: git trailer to
link to a bug related to the patch.
The email-to-bugzilla script does not understand this
convention, so we also still write "PR mumble/NNNN".
Could you patch email-to-bugzilla to handle this?
I'm attaching a patch that I think should work.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-01-20 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 16:29 tromey at sourceware dot org [this message]
2023-01-20 16:33 ` [Bug Infrastructure/30029] " simark at simark dot ca
2023-02-07 18:10 ` tromey at sourceware dot org
2023-02-07 18:17 ` fche at redhat dot com
2023-02-07 19:15 ` mark at klomp dot org
2023-02-08 2:13 ` tromey at sourceware dot org
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=bug-30029-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.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).