Bug 30030 - Connect gdb bugzilla to gdb-patches public inbox
Summary: Connect gdb bugzilla to gdb-patches public inbox
Status: NEW
Alias: None
Product: sourceware
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: overseers mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-20 16:29 UTC by Tom Tromey
Modified: 2023-01-20 16:29 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Tromey 2023-01-20 16:29:33 UTC 
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.