[RFC] Auto-posting committed patches to this list?
Carlos O'Donell
carlos@redhat.com
Tue Mar 16 03:55:15 GMT 2021
On 3/15/21 11:52 PM, Siddhesh Poyarekar wrote:
> On 3/16/21 7:54 AM, Carlos O'Donell wrote:
>>> This is not just to make the patchwork backlog cleaner, but also
>>> to make sure that the community is aware of the final version of
>>> the patch that went in; they're easier to correlate in the same
>>> list since they'd typically have the same subject line.
>>
>> How will it make the patchwork backlog cleaner?
>
> This action in itself won't, but it will enable other actions later
> on. Once we have 1:1 correspondence between patchwork and the repo,
> we could then have more aggressive actions that mark patches with
> similar subject lines (especially ones that are in Changes Requested
> or some other non-terminal state) from the author as Superseded,
> automating at least some of the developer workflow.
Perfect. Completely understood.
> I'll set up a cron job to send out these patches first and we can
> then build on it.
Thanks!
--
Cheers,
Carlos.
More information about the Libc-alpha
mailing list