From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30030] New: Connect gdb bugzilla to gdb-patches public inbox
Date: Fri, 20 Jan 2023 16:29:33 +0000 [thread overview]
Message-ID: <bug-30030-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30030
Bug ID: 30030
Summary: Connect gdb bugzilla to gdb-patches public inbox
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: ---
Right now, gdb has a commit script on sourcware that looks
for bugzilla references like "PR blah/NNNN"; and then it
records the commit information in bugzilla (but see bug #30029).
It would be nice for gdb to extend this treatment to patches.
More than once, we've lost a patch and then, much later,
had to dig it out of the mail archives. If the patch
had been recorded in bugzilla when sent, it would have been
much more convenient.
The idea here is to use the same logic from the commit script
to scan email to gdb-patches; then put a link to public inbox
(presumably using the message-id) into the correct bug in
bugzilla.
Public inbox is preferred here because I think it does a
better job at associating a message-id to a thread than
the other mail archive.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2023-01-20 16:29 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=bug-30030-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).