Re: [PATCH 1/4] gdb: make discrete_position return optional

[Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>]

On 2020-12-08 6:41 a.m., Maciej W. Rozycki wrote:
>  FWIW at <https://patchwork.sourceware.org/project/gdb/> we have a working 
> instance of patchwork too that can be used to track own and other people's 
> submissions, which also has been recently brought up to date as far as the 
> engine is concerned, thanks to people using it actively for the glibc 
> project.  They've even set up a weekly meeting recently to review patches:
> <https://sourceware.org/glibc/wiki/PatchworkReviewMeetings>.  That might 
> be something to consider I believe for patch management.

Yes, I think we should use it!

But our previous experience with Patchwork is that it's a lot of work to
manage patches to keep Patchwork in a good state.  When you send a v2, v3,
v4 of a series, it creates new patches, and someone needs to manually go
set the older ones as "Superseded".  And when then patches get merged,
someone needs to go mark them as "Merged" so they go away.

Is this how it still works?

If Patchwork could do that somewhat automatically and reliably (say, by
relying on same the Change-Ids as Gerrit uses), I think it would be
wonderful.

Last time I checked [1], the upstream project was open to receive such
contributions, but of course it takes some effort to implement.

[1 https://github.com/getpatchwork/patchwork/issues/327

Simon