From: Kate Stewart <kstewart@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-spdx@vger.kernel.org
Subject: Re: Workflow
Date: Fri, 10 May 2019 08:01:12 -0500 [thread overview]
Message-ID: <CAG_66ZTEaBEuRVR32+pT-4AmTatvNK2jkBgondsmAemSe8-5Xg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1905092349010.1763@nanos.tec.linutronix.de>
On Thu, May 9, 2019 at 4:56 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> Kate,
>
> On Thu, 9 May 2019, Kate Stewart wrote:
> > On Thu, May 9, 2019 at 9:11 AM Thomas Gleixner <tglx@linutronix.de> wrote:
> > > Any opinions on the size of the batches and how long it will take to get
> > > the reviews done or any other suggestions for a workable solution?
> >
> > Grouping them in digestible sets, and organizing each patch around a
> > pattern makes sense to me. +1
>
> I appreciate the +1, but I would appreciate even more some hint what you
> think is a digestible set size and how much time you think it takes to
> review such a set. You know that this is just a question of time.
Heh, fair enough. I meant I am fine with the proposal of 10-25 a
day you outlined.
Biasing more to the 25 side is ok - sooner we're through the bulk of
them the better. :-)
Thanks, Kate
next prev parent reply other threads:[~2019-05-10 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 14:11 Workflow Thomas Gleixner
2019-05-09 14:45 ` Workflow Kate Stewart
2019-05-09 21:56 ` Workflow Thomas Gleixner
2019-05-10 9:25 ` Workflow Allison Randal
2019-05-10 10:54 ` Workflow Thomas Gleixner
2019-05-10 11:02 ` Workflow Allison Randal
2019-05-10 13:01 ` Kate Stewart [this message]
2019-05-10 13:18 ` Workflow Bradley M. Kuhn
2019-05-10 9:06 ` Workflow Greg KH
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=CAG_66ZTEaBEuRVR32+pT-4AmTatvNK2jkBgondsmAemSe8-5Xg@mail.gmail.com \
--to=kstewart@linuxfoundation.org \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 NNTP newsgroup(s).