From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2/next 2/4] DEVELOPERS: add initial list of Buildroot developers
Date: Tue, 23 Aug 2016 16:50:41 -0300 (BRT) [thread overview]
Message-ID: <1065867889.672166.1471981841582.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <1471956466-22338-3-git-send-email-thomas.petazzoni@free-electrons.com>
> From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
---8<---
> This is an initial list of Buildroot developers. It has been created
> semi-automatically by parsing the Git history, and finding the authors
> of commits with a title like "<foo>: new package". Some additional
> manual tweaking has been done (merging multiple entries corresponding to
> the same person, adding some more entries, etc.).
---8<---
> +N: Carlos Santos <casantos@datacom.ind.br>
> +F: package/gmock/
> +F: package/perl-file-util/
I can take care of util-linux, too.
---8<---
> +N: Giovanni Zantedeschi <giovanni.zantedeschi@datacom.ind.br>
> +F: package/libpam-radius-auth/
> +F: package/libpam-tacplus/
Giovanni does not work at DATACOM anymore. Please replace by casantos at ...
---8<---
> +N: Stephan Hoffmann <sho@relinux.de>
> +F: package/cache-calibrator/
> +F: package/gtest/
I'm planing to replace gmock and gtest by "googletest" in the near future, so I could take care of gtest if Stefan does not mind.
---8<---
Carlos Santos (Casantos)
DATACOM, P&D
next prev parent reply other threads:[~2016-08-23 19:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 12:47 [Buildroot] [PATCHv2/next 0/4] DEVELOPERS file and get-developer tool Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 1/4] support/scripts/get-developers: add new script Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 2/4] DEVELOPERS: add initial list of Buildroot developers Thomas Petazzoni
2016-08-23 14:26 ` Gary Bisson
2016-08-23 20:15 ` Thomas Petazzoni
2016-08-23 17:38 ` Bernd Kuhls
2016-08-23 20:16 ` Thomas Petazzoni
2016-08-23 19:50 ` Carlos Santos [this message]
2016-08-23 20:25 ` Thomas Petazzoni
2016-08-23 19:51 ` Romain Naour
2016-08-23 20:30 ` Thomas Petazzoni
2016-08-23 21:01 ` Peter Korsgaard
2016-08-23 21:40 ` Thomas Petazzoni
2016-08-23 21:54 ` Peter Korsgaard
2016-08-23 21:59 ` Thomas Petazzoni
2016-08-24 0:17 ` Arnout Vandecappelle
2016-08-24 9:58 ` Peter Korsgaard
2016-08-24 14:04 ` Thomas Petazzoni
2016-08-24 14:04 ` Thomas Petazzoni
2016-08-24 6:38 ` Rahul Bedarkar
2016-08-24 14:06 ` Thomas Petazzoni
2016-08-24 13:35 ` Alistair Francis
2016-08-24 14:09 ` Thomas Petazzoni
2016-08-24 20:26 ` Alistair Francis
2016-08-29 10:19 ` Julien Boibessot
2016-08-29 11:22 ` Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 3/4] docs/manual: update contribute.txt to cover get-developers Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer Thomas Petazzoni
2016-08-24 0:21 ` Arnout Vandecappelle
2016-08-24 14:22 ` Thomas Petazzoni
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=1065867889.672166.1471981841582.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--cc=buildroot@busybox.net \
/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