qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH  v1 0/6] current state of gitdm/next
Date: Tue, 26 Feb 2019 16:44:54 +0000	[thread overview]
Message-ID: <20190226164500.8080-1-alex.bennee@linaro.org> (raw)

Hi,

I had a few patches sat in my queue so I spent a little time doing
some email address archaeology and cleaning up the gitdm output. Some
of these are guesses so I won't be including them in a pull-request
until I get confirmation from the various contributors.

For reference the current contributor base for the last year looks
like:

  Top changeset contributors by employer
  Red Hat                   3181 (43.6%)
  Linaro                    1292 (17.7%)
  (None)                     414 (5.7%)
  IBM                        384 (5.3%)
  Academics (various)        257 (3.5%)
  Wave Computing             202 (2.8%)
  Virtuozzo                  170 (2.3%)
  Oracle                      89 (1.2%)
  Intel                       87 (1.2%)
  Cadence Design Systems      82 (1.1%)

The following patches need review
  0003/contrib gitdm add some more people academic group.patch
  0004/contrib gitdm add more individual contributors.patch
  0005/contrib gitdm another IBM email.patch
  0006/contrib gitdm another non corporate email from Re.patch

Aleksandar Markovic (2):
  contrib: gitdm: Update domain-map
  contrib: gitdm: Update Wave Computing group

Alex Bennée (4):
  contrib: gitdm: add some more people academic group
  contrib: gitdm: add more individual contributors
  contrib: gitdm: another IBM email
  contrib: gitdm: another non-corporate email from RedHat

 contrib/gitdm/domain-map            |  5 +++++
 contrib/gitdm/group-map-academics   |  9 +++++++++
 contrib/gitdm/group-map-ibm         |  1 +
 contrib/gitdm/group-map-individuals |  2 ++
 contrib/gitdm/group-map-redhat      |  1 +
 contrib/gitdm/group-map-wavecomp    | 12 ++++++++++++
 6 files changed, 30 insertions(+)

-- 
2.20.1

             reply	other threads:[~2019-02-26 16:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 16:44 Alex Bennée [this message]
2019-02-26 16:44 ` [Qemu-devel] [PATCH v1 1/6] contrib: gitdm: Update domain-map Alex Bennée
2019-02-26 16:44 ` [Qemu-devel] [PATCH v1 2/6] contrib: gitdm: Update Wave Computing group Alex Bennée
2019-02-26 16:44 ` [Qemu-devel] [PATCH v1 3/6] contrib: gitdm: add some more people academic group Alex Bennée
2019-02-26 16:46   ` Samuel Thibault
2019-02-26 17:11     ` Alex Bennée
2019-02-26 17:12       ` Samuel Thibault
2019-02-26 22:02   ` Aurelien Jarno
2019-02-26 22:21   ` BALATON Zoltan
2019-02-26 16:44 ` [Qemu-devel] [PATCH v1 4/6] contrib: gitdm: add more individual contributors Alex Bennée
2019-02-26 16:44 ` [Qemu-devel] [PATCH v1 5/6] contrib: gitdm: another IBM email Alex Bennée
2019-02-26 16:45 ` [Qemu-devel] [PATCH v1 6/6] contrib: gitdm: another non-corporate email from RedHat Alex Bennée
2019-02-26 18:42   ` Marcel Apfelbaum
2019-02-26 19:55     ` Alex Bennée
2019-02-27  8:53       ` Marcel Apfelbaum

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=20190226164500.8080-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.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).