* [Bug Infrastructure/30030] New: Connect gdb bugzilla to gdb-patches public inbox
@ 2023-01-20 16:29 tromey at sourceware dot org
0 siblings, 0 replies; only message in thread
From: tromey at sourceware dot org @ 2023-01-20 16:29 UTC (permalink / raw)
To: overseers
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-01-20 16:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-20 16:29 [Bug Infrastructure/30030] New: Connect gdb bugzilla to gdb-patches public inbox tromey at sourceware dot org
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).