[RFC] Updating patchwork patches on commit

[Girish Joshi]

I've created this[1] script to go through all available series and get
the patches that do not belong to any one of them.
It dumps a json containing individual patch ids in /tmp directory.
This script can be merged with the previous one "apply-patches.py".
I'll do that soon.
Currently we have around 106 individual patches with the state "new"
that do not belong to any of the series.

Girish Joshi
girishjoshi.io

On Sat, Dec 19, 2020 at 6:55 PM Girish Joshi <girish946@gmail.com> wrote:
>
> On Fri, Dec 18, 2020 at 9:34 AM Siddhesh Poyarekar <siddhesh@gotplt.org> wrote:
> >
> > On 12/17/20 11:19 PM, Girish Joshi wrote:
> > > Hi Siddhesh,
> > > On Thu, Dec 17, 2020 at 12:19 AM Siddhesh Poyarekar <siddhesh@gotplt.org> wrote:
> > >> I'm surprised there are 1114 series that need action; maybe it's
> > >> including series that have already been committed and you need to filter
> > >> those out?
> > > Yeah, in the git output we can see that a lot of those are already applied.
> >
> > Are they marked as committed though?  If not then they should be.
> Yes, the status for (almost all of) those patches is "committed" on
> the patchwork instance.
> To verify it I'm writing down the IDs for such series in a separate file now.
> Although I did not find an option from the git-pw cli for checking if
> a series is already committed.
> The work around for that could be to go through all of the patches in
> that series and check if all of them are committed.
>
> Girish Joshi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: check-series.py
Type: text/x-python
Size: 2980 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20201222/c79a5da3/attachment-0001.py>