[Bug Infrastructure/30042] patchworks should automatically notice a pushed patch

["mark at klomp dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30042

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Tom Tromey from comment #3)
> (In reply to Carlos O'Donell from comment #1)
> 
> > 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.
> 
> 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 scripts
> > that they need.
> 
> 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.