All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/4] Add a get-developers script and database
Date: Mon, 12 Sep 2016 23:14:50 +0200	[thread overview]
Message-ID: <20160912211450.GB15314@free.fr> (raw)
In-Reply-To: <1473713695-2611-1-git-send-email-thomas.petazzoni@free-electrons.com>

Thomas, All,

On 2016-09-12 22:54 +0200, Thomas Petazzoni spake thusly:
> This is the third version of the patch series adding a get-developers
> script and the corresponding DEVELOPERS database.

All I want to say is, just commit that already! ;-)

Seriously, this thing is working: we've been receiving notifications for
some time now.

It will not be easy for you to maintain the developpers file locally, so
if we want people to register as developpers, we need to have that in
the tree.

Any remaining nit can be fixed afterward.

Regards,
Yann E. MORIN.

> Since v2, the DEVELOPERS database has seen numerous updates, following
> the feedback from several Buildroot developers.
> 
> Thanks,
> 
> Thomas
> 
> Thomas Petazzoni (4):
>   support/scripts/get-developers: add new script
>   DEVELOPERS: add initial list of Buildroot developers
>   docs/manual: update contribute.txt to cover get-developers
>   docs/manual: add new section about the DEVELOPERS file and
>     get-developer
> 
>  DEVELOPERS                         | 1581 ++++++++++++++++++++++++++++++++++++
>  docs/manual/contribute.txt         |   18 +-
>  docs/manual/developers.txt         |   46 ++
>  docs/manual/manual.txt             |    2 +
>  support/scripts/get-developers     |   83 ++
>  support/scripts/getdeveloperlib.py |  201 +++++
>  6 files changed, 1929 insertions(+), 2 deletions(-)
>  create mode 100644 DEVELOPERS
>  create mode 100644 docs/manual/developers.txt
>  create mode 100755 support/scripts/get-developers
>  create mode 100644 support/scripts/getdeveloperlib.py
> 
> -- 
> 2.7.4
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2016-09-12 21:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 20:54 [Buildroot] [PATCH v3 0/4] Add a get-developers script and database Thomas Petazzoni
2016-09-12 20:54 ` [Buildroot] [PATCH v3 1/4] support/scripts/get-developers: add new script Thomas Petazzoni
2016-09-15 20:28   ` Arnout Vandecappelle
2016-09-21  7:03   ` Peter Korsgaard
2016-09-21  8:50     ` Thomas Petazzoni
2016-09-21  9:25       ` Arnout Vandecappelle
2016-09-12 20:54 ` [Buildroot] [PATCH v3 2/4] DEVELOPERS: add initial list of Buildroot developers Thomas Petazzoni
2016-09-21  7:04   ` Peter Korsgaard
2016-09-12 20:54 ` [Buildroot] [PATCH v3 3/4] docs/manual: update contribute.txt to cover get-developers Thomas Petazzoni
2016-09-12 21:09   ` Yann E. MORIN
2016-09-15 20:29     ` Arnout Vandecappelle
2016-09-21  7:07   ` Peter Korsgaard
2016-09-12 20:54 ` [Buildroot] [PATCH v3 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer Thomas Petazzoni
2016-09-15 20:35   ` Arnout Vandecappelle
2016-09-21  7:17   ` Peter Korsgaard
2016-09-12 21:14 ` Yann E. MORIN [this message]
2016-09-12 21:30   ` [Buildroot] [PATCH v3 0/4] Add a get-developers script and database 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=20160912211450.GB15314@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 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.