From: Thomas Gleixner <tglx@linutronix.de>
To: linux-spdx@vger.kernel.org
Subject: Status week 2
Date: Mon, 3 Jun 2019 00:10:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1906022332280.30817@nanos.tec.linutronix.de> (raw)
Folks,
thanks again for wading through this maze.
Week 1 Week 2 Total
Number of patches/patterns reviewed: 125 193 318
Number of patches/patterns sorted out: 19 27 46
Number of patches/patterns found ok: 106 166 272
Number of files affected: 2010 10413 12423
Number of deleted lines: 21631 80870 102501
Number of deleted lines per file (average): 10.7 7.7 8.3
Number of bytes removed: 1075891 4015498 5091389
Linus tree: v5.2-rc1 v5.2-rc2 v5.2-rc3
Patches merged: 0 109 190
SPDX Coverage: 37% 45% 57%
With the already collected 85 patches from this week which are pending for
merge (batch11 - 13) the SPDX coverage goes up to 61%.
Batch 14/15 are not yet accounted as there is review in progress.
Thanks,
tglx
reply other threads:[~2019-06-02 22:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.21.1906022332280.30817@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-spdx@vger.kernel.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 NNTP newsgroup(s).