All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/4] DEVELOPERS: add initial list of Buildroot developers
Date: Tue, 23 Aug 2016 13:44:38 +0200	[thread overview]
Message-ID: <20160823134438.550a0616@free-electrons.com> (raw)
In-Reply-To: <CAFOYHZDQpZWxo4rAAuXj6JDhOLcmRPb=19+_JWC_jKS_8vmpRQ@mail.gmail.com>

Hello,

On Tue, 23 Aug 2016 22:47:39 +1200, Chris Packham wrote:
> Hi Thomas,
> 
> 2016-08-23 9:51 GMT+12:00 Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>:
> > 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.).
> >
> > +N:     Chris Packham <judge.packham@gmail.com>
> > +F:     package/eventlog/
> > +F:     package/micropython/  
> 
> Probably want to add package/micropython/-lib/ and package/syslog-ng/
> unless someone else wants them.

Since you are the original authors of those packages, I was wondering
why my script that parsed the Git history didn't find those ones. It's
because:

	micropython-lib: new packages

there's a final "s" here which didn't match my script regexp.

And:

	syslog-ng: New package

there's a capital "N" in New which my regexp also wasn't taking into
account.

I've added you as the contact developer for those two packages. Thanks
for the feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-23 11:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 21:51 [Buildroot] [PATCH/next 0/4] DEVELOPERS file and get-developer tool Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 1/4] support/scripts/get-developers: add new script Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 2/4] DEVELOPERS: add initial list of Buildroot developers Thomas Petazzoni
2016-08-23  4:33   ` Baruch Siach
2016-08-23 10:03     ` Thomas Petazzoni
2016-08-23  5:41   ` Bernd Kuhls
2016-08-23 10:03     ` Luca Ceresoli
2016-08-23 10:03     ` Thomas Petazzoni
2016-08-23  8:56   ` Sébastien Szymanski
2016-08-23 10:09   ` Luca Ceresoli
2016-08-23 11:41     ` Thomas Petazzoni
2016-08-23 13:01       ` Luca Ceresoli
2016-08-23 17:54       ` [Buildroot] Future of linphone package, was: " Bernd Kuhls
2016-08-23 19:50         ` Thomas Petazzoni
2016-08-23 20:54           ` Peter Korsgaard
2016-08-24  0:23             ` Arnout Vandecappelle
2016-08-24  7:44               ` Peter Korsgaard
2016-08-24  9:06                 ` Luca Ceresoli
2016-08-23 10:47   ` [Buildroot] " Chris Packham
2016-08-23 11:44     ` Thomas Petazzoni [this message]
2016-08-24  0:54   ` Rodrigo Rebello
2016-08-24 16:44     ` Thomas Petazzoni
2016-08-24  7:12   ` François Perrad
2016-08-24 16:49     ` Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 3/4] docs/manual: update contribute.txt to cover get-developers Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer 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=20160823134438.550a0616@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 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.