From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2/next 2/4] DEVELOPERS: add initial list of Buildroot developers
Date: Tue, 23 Aug 2016 23:59:59 +0200 [thread overview]
Message-ID: <20160823235959.2a242a36@free-electrons.com> (raw)
In-Reply-To: <87y43ngnic.fsf@dell.be.48ers.dk>
Hello,
On Tue, 23 Aug 2016 23:54:03 +0200, Peter Korsgaard wrote:
> Ahh, ok. And your script really looks for something like
>
> '<foo>: new package' and not just the first commit for for E.G. every
> .mk file?
Yes, I've looked at "<foo>: new package" commits. Looking at the first
commit if each .mk file would have been a better approach indeed. I can
try to have a look at this alternative approach, and see if it brings
some additional/better details.
> > Thanks for the feedback!
>
> You're welcome, the series looks OK to me.
Thanks. I believe the Python code could definitely get some review, but
follow-up patches are also possible to improve the implementation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-23 21:59 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
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 [this message]
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=20160823235959.2a242a36@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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