From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Girish Joshi <girish946@gmail.com>,
Girish Joshi via Libc-alpha <libc-alpha@sourceware.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [RFC] Updating patchwork patches on commit
Date: Fri, 12 Feb 2021 14:32:13 +0530 [thread overview]
Message-ID: <39b10e24-a6b3-e6d7-adc3-2c8271ec1e1b@gotplt.org> (raw)
In-Reply-To: <CALkY8p97h9XP7d4pWw3bd1Fa7PoGBccs1QCg7d9aPqB6SrBxGQ@mail.gmail.com>
On 2/4/21 9:17 PM, Girish Joshi wrote:
>> Once this is done, this script can be invoked after a regular interval
>> of time to check if the new patches can be applied.
> We can do this now.
>
> There are a couple of functions that need refactoring.
> But for now it does the job.
> Could you please review it?
The script is now done and I have gone through the outputs. Some notes:
1. git-pw runs are leaving /tmp/git-pw* directories, you need to clean
them up
2. The script must ignore patches that are not in the New state.
Currently it seems to be going through everything.
3. The output in pw-results seemed to mostly be old patches from 2014 or
so by default. Perhaps it's hitting the limit for the server in 2014
because it's not filtering correctly on patch state?
If the output does not correspond with what you're seeing, then please
send the commandline you'd like me to run to get the output you're
seeing. The primary goal with this script set is to identify patches in
2019/2020 that are out of date and no longer apply so that we can mark
them accordingly.
Thanks,
Siddhesh
next prev parent reply other threads:[~2021-02-12 9:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 5:48 Siddhesh Poyarekar
2020-12-07 8:45 ` Florian Weimer
2020-12-07 9:30 ` Siddhesh Poyarekar
2020-12-07 16:15 ` DJ Delorie
2020-12-07 16:39 ` Siddhesh Poyarekar
2020-12-07 17:02 ` DJ Delorie
2020-12-07 18:11 ` Joseph Myers
2020-12-08 2:57 ` Siddhesh Poyarekar
2020-12-08 9:08 ` Andreas Schwab
2020-12-08 10:10 ` Siddhesh Poyarekar
2020-12-16 18:35 ` Girish Joshi
2020-12-16 18:49 ` Siddhesh Poyarekar
2020-12-17 17:49 ` Girish Joshi
2020-12-18 4:04 ` Siddhesh Poyarekar
2020-12-19 13:25 ` Girish Joshi
2020-12-22 15:13 ` Girish Joshi
2021-01-06 20:26 ` Girish Joshi
2021-02-04 15:47 ` Girish Joshi
2021-02-12 5:25 ` Siddhesh Poyarekar
2021-02-12 9:02 ` Siddhesh Poyarekar [this message]
2021-02-12 13:04 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39b10e24-a6b3-e6d7-adc3-2c8271ec1e1b@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=girish946@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).