From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"cota@braap.org" <cota@braap.org>
Subject: Re: [Qemu-devel] [PATCH v1 0/3] gitdm updates
Date: Wed, 9 Jan 2019 23:43:54 +0100 [thread overview]
Message-ID: <CAL1e-=hh2LYxKVUZzP0AnHQUa_rbyOmNJhXcnvUPSEsgEBKvGA@mail.gmail.com> (raw)
In-Reply-To: <CAL1e-=g47ATjpGJpM_PivAdQQ=wk=j3rmM1=vVL+2xQ5XFo1NQ@mail.gmail.com>
On Tuesday, January 8, 2019, Aleksandar Markovic <
aleksandar.m.mail@gmail.com> wrote:
>
>
> On Monday, January 7, 2019, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>>
>> Hi,
>>
>> Added a few more updates mostly of IBMers with non corporate emails.
>
>
> Hi, Alex, could you please add
>
> leon.alrae@imgtec.com
>
> to Wave Computing group?
>
> (my email client automatically inserts and displays "ae" as one letter,
> the last name should be ending with a e, a-l-r-a-e.)
>
> I have some patches from Leon that will be upstreamed soon, with his email
> as above.
>
> I am on days-off and it is difficult for me to create and send patches, so
> I ask you toake this minor correction.
>
> Thanks, Aleksandar
>
>
>
>> The year-end stats as per:
>>
>> git log --numstat --after="1/1/2018 00:00" \
>> --before="31/12/2018 23:59" | gitdm -n -l 10
>>
>> Are:
>>
>> Top changeset contributors by employer
>> Red Hat 3091 (43.3%)
>> Linaro 1201 (16.8%)
>> (None) 484 (6.8%)
>> IBM 426 (6.0%)
>> Academics (various) 186 (2.6%)
>> Virtuozzo 172 (2.4%)
>> Wave Computing 118 (1.7%)
>> Igalia 109 (1.5%)
>> Xilinx 102 (1.4%)
>> Cadence Design Systems 80 (1.1%)
>>
>> Top lines changed by employer
>> Red Hat 140523 (30.3%)
>> Cadence Design Systems 81010 (17.5%)
>> Linaro 78098 (16.8%)
>> Wave Computing 33134 (7.1%)
>> IBM 18918 (4.1%)
>> SiFive 14436 (3.1%)
>> Academics (various) 11995 (2.6%)
>> (None) 11458 (2.5%)
>> Virtuozzo 10770 (2.3%)
>> Oracle 6698 (1.4%)
>>
>> Alex Bennée (2):
>> contrib/gitdm: add Nokia and Proxmox to the domain-map
>> contrib/gitdm: add two more IBM'ers to group-map-ibm
>>
>> Joel Stanley (1):
>> contrib/gitdm: Add other IBMers
>>
>> contrib/gitdm/domain-map | 2 ++
>> contrib/gitdm/group-map-ibm | 7 +++++++
>> 2 files changed, 9 insertions(+)
>>
>> --
>> 2.17.1
>>
>>
>>
If you create a patch for Wave Computing as I described it also has:
Reviewed-by: Aleksandar Markovic <amarkovic@wavecomp.com>
next prev parent reply other threads:[~2019-01-09 22:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 11:11 [Qemu-devel] [PATCH v1 0/3] gitdm updates Alex Bennée
2019-01-07 11:11 ` [Qemu-devel] [PATCH v1 1/3] contrib/gitdm: add Nokia and Proxmox to the domain-map Alex Bennée
2019-01-09 22:41 ` Aleksandar Markovic
2019-01-07 11:11 ` [Qemu-devel] [PATCH v1 2/3] contrib/gitdm: Add other IBMers Alex Bennée
2019-01-09 22:40 ` Aleksandar Markovic
2019-01-07 11:11 ` [Qemu-devel] [PATCH v1 3/3] contrib/gitdm: add two more IBM'ers to group-map-ibm Alex Bennée
2019-01-09 22:32 ` Aleksandar Markovic
2019-01-08 12:44 ` [Qemu-devel] [PATCH v1 0/3] gitdm updates Aleksandar Markovic
2019-01-09 22:43 ` Aleksandar Markovic [this message]
2019-01-14 15:58 ` Alex Bennée
2019-01-14 17:23 ` Aleksandar Markovic
2019-01-11 16:34 ` Aleksandar Markovic
2019-01-11 18:00 ` Alex Bennée
2019-01-14 6:56 ` Markus Armbruster
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='CAL1e-=hh2LYxKVUZzP0AnHQUa_rbyOmNJhXcnvUPSEsgEBKvGA@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.