From: Girish Joshi <girish946@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Girish Joshi via Libc-alpha <libc-alpha@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [RFC] Updating patchwork patches on commit
Date: Sat, 19 Dec 2020 18:55:35 +0530 [thread overview]
Message-ID: <CALkY8p84=rjOszpxb9QbeKbzWMwriJhLKungt+-Mr5A8jk7Qpw@mail.gmail.com> (raw)
In-Reply-To: <9163662f-4f00-bb6f-6451-a8fd9951613d@gotplt.org>
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 prev parent reply other threads:[~2020-12-19 13:25 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 [this message]
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
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='CALkY8p84=rjOszpxb9QbeKbzWMwriJhLKungt+-Mr5A8jk7Qpw@mail.gmail.com' \
--to=girish946@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.org \
--cc=siddhesh@gotplt.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).