unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Review promise :-)
Date: Thu, 13 Feb 2020 11:19:05 -0500	[thread overview]
Message-ID: <CAEMqeSoP1xpdqx+Qs954iSu0UVHHSbhPfv5wuH6frDjYwHuf=Q@mail.gmail.com> (raw)
In-Reply-To: <CAKCAbMgafVyNz3b5CmM+ft0=5+qq3tb3LfvotdoD4yr6Wa6ZcQ@mail.gmail.com>

On Thu, Feb 13, 2020 at 11:01 AM Zack Weinberg <zackw@panix.com> wrote:
>
> On Thu, Feb 13, 2020 at 9:57 AM Carlos O'Donell <carlos@redhat.com> wrote:
> >
> > Increasingly I'm actually turning to patchwork to look for patches to
> > review. I'm trying to structure my work day around an eventual attempt
> > to use Patchwork 2.0.
> >
> > For example I was looking for patches from H.J. to review and I
> > cleaned up his list of owned patches in patchwork to track down what
> > still needed review and committing.
> >
> > This was actually quite a nice way to work and is the kind of workflow
> > I wanted to have in place with gerritt but this works with email.
> >
> > The hard part is that each developers queue is messy because we don't
> > keep them clean.
>
> Is there a way to operate on lots of patches at once?  My queue is
> full of old patches that should be marked either committed or dropped,
> it would be nice to not have to load the individual patch page for
> each one and push the same buttons for each.

Yeah, absolutely.

You have two options:
* Script it using the pwclient CLI
* Use the web interface, apply a filter, click the top "Patch"
checkmark to check all selected, then apply a property and it is
applied to all the selected patches.

Cheers,
Carlos.


  parent reply	other threads:[~2020-02-13 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 14:56 Review promise :-) Carlos O'Donell
2020-02-13 15:03 ` Florian Weimer
2020-02-13 15:06   ` Carlos O'Donell
2020-02-13 15:44     ` Siddhesh Poyarekar
2020-02-13 15:47       ` Siddhesh Poyarekar
2020-02-13 16:01 ` Zack Weinberg
2020-02-13 16:17   ` Florian Weimer
2020-02-13 16:19   ` Carlos O'Donell [this message]
2020-02-13 17:42     ` Zack Weinberg
2020-02-13 17:57       ` Florian Weimer
2020-02-13 18:12         ` Zack Weinberg
     [not found]           ` <CAKCAbMi9bejmEgsrQcHau0uwU8Dc42FwFz3Wf6-4Qxyw4WE1hw@mail.gmail.com>
2020-02-13 18:20             ` Carlos O'Donell
2020-02-13 18:31               ` Zack Weinberg
2020-02-14  8:43                 ` Stefan Liebler
2020-02-14 16:48                   ` Carlos O'Donell
2020-02-17  7:38                     ` Stefan Liebler
2020-02-13 20:54 ` Joseph Myers
2020-02-14  1:12   ` 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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEMqeSoP1xpdqx+Qs954iSu0UVHHSbhPfv5wuH6frDjYwHuf=Q@mail.gmail.com' \
    --to=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zackw@panix.com \
    /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).