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: Wed, 24 Aug 2016 16:09:53 +0200 [thread overview]
Message-ID: <20160824160953.2dadd32e@free-electrons.com> (raw)
In-Reply-To: <CAKmqyKOYZuW7WeHmP7iatLPJzEudzEnnxnDJYi5oWt=uDTQQkA@mail.gmail.com>
Hello,
On Wed, 24 Aug 2016 09:35:27 -0400, Alistair Francis wrote:
> > +N: Alistair Francis <alistair.francis@xilinx.com>
> > +F: package/xen/
> > +
>
> Can I please have a second email added?
>
> Alistair Francis <alistair23@gmail.com>
>
> I need to keep my company email here, but it is much easier to do list
> work from my gmail. If not what's here now is fine.
Having two e-mail addresses is currently not supported, but it can
probably be added without too much efforts, though I'm not sure to do
it for this version of the patch series (and rather handle that as a
possible future improvement). Would this be OK?
In fact, thinking about this, using simply a comma to separate both
e-mail addresses might even work as-is, but I would have to test first.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-24 14:09 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
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 [this message]
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=20160824160953.2dadd32e@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