From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A85D33858D1E; Fri, 20 Jan 2023 16:29:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A85D33858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1674232173; bh=28VFSwAwzprX+9CVMWYcNM4iWnCbDVF8Y3ttfcOoZRk=; h=From:To:Subject:Date:From; b=Xb/VL0mkJ52hLvQ56C+GetXNFSR5yJNaI2UTTvwE5Tyfz821oMxX9QxxdiRmPDG70 jx42fA7k7V+V8g7m+Ox5FdVE8Dom2So4nRH/Fj8l+UXn6xXJp8M9Wisc4Iv05sLJ7V jhW24JzWkj9DSQf1ayoV82Tcmhx5TZVc53he8yhs= From: "tromey at sourceware dot 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30030 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. --=20 You are receiving this mail because: You are the assignee for the bug.=