From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 214223858D39; Tue, 24 Jan 2023 22:07:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 214223858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1674598048; bh=oVclN9Li1H91NHiT082jGg2tAphbKf9FLKxCjk0RFdo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mYsxrpFG/vDYOnCVkvNdHWNsY8P2KSNsR8RxWq3bOR+3qeD6ygkRftv12RPw3PSrB y/yFkoG3B0HhL0rKfGnJemykXy87ZvWujDgDXITTUUj5f3vO0Jaiha0XrwJZvwi5VH St3GTlWTEMggEsOo1x98YtdkIVx+gTCubC8ZvADg= From: "mark at klomp dot org" To: overseers@sourceware.org Subject: [Bug Infrastructure/30042] patchworks should automatically notice a pushed patch Date: Tue, 24 Jan 2023 22:07:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed 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: mark at klomp 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: cc Message-ID: In-Reply-To: References: 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=3D30042 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --- Comment #4 from Mark Wielaard --- (In reply to Tom Tromey from comment #3) > (In reply to Carlos O'Donell from comment #1) >=20 > > The first problem we saw here was that it requires discipline from the > > community to commit *exactly* what was posted and agreed upon in order = to > > make the checking less error prone. >=20 > This would work fine for [pushed] patches, which seems good enough for > this ticket. yeah, one step at a time. Siddhesh script could be run under gdbadmin or we could do it from the buildbot since we build each gdb commit on push. > For other patches, this seems like more work because it means there > will have to be one final series sent, but patchworks is also bad about > removing old series. We could have a separate script or mail filter that checks for patches that supersede a previous patch/series (check subject is the same modulo vX+1). > > In either (1) or (2) I think this is up to the projects to run the scri= pts > > that they need. >=20 > Are you saying this shouldn't be a sourceware PR? > I can close it if so. We could move it to the gdb product, but lets keep it open here to document= the steps we did so other projects can adopt them if they like. --=20 You are receiving this mail because: You are the assignee for the bug.=