From: Allison Randal <allison@lohutok.net>
To: Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>
Cc: linux-spdx@vger.kernel.org
Subject: Re: Workflow
Date: Fri, 10 May 2019 10:25:26 +0100 [thread overview]
Message-ID: <4a141f36-7d4a-3a4c-259d-d11174f7e24c@lohutok.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1905092349010.1763@nanos.tec.linutronix.de>
On 5/9/19 10:56 PM, Thomas Gleixner wrote:
>
> 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.
I'm fine with the 10-25/day you suggested, as long as I know to expect
them. I'll just do a quick run with my morning coffee. Personally, I'm
also fine if you just want to do all 500+ at once, and I'll work my way
through them in larger batches (dealing with several thousand emails a
day is not unusual for me, and these are quick reviews that don't need a
substantial reply). But, I suspect you're right that smaller batches
will be easier for most people.
I will use the git URL to look at the actual changes, because my brain
is trained to think in diffs, but I'll only review the first few files
in each diff as a sample.
Allison
next prev parent reply other threads:[~2019-05-10 9:25 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 ` Allison Randal [this message]
2019-05-10 10:54 ` Workflow Thomas Gleixner
2019-05-10 11:02 ` Workflow Allison Randal
2019-05-10 13:01 ` Workflow Kate Stewart
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=4a141f36-7d4a-3a4c-259d-d11174f7e24c@lohutok.net \
--to=allison@lohutok.net \
--cc=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).