Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] DEVELOPERS: add Martin Bark for package/nodejs
Date: Sun, 5 Mar 2017 12:13:29 +0100	[thread overview]
Message-ID: <20170305121329.639183c8@free-electrons.com> (raw)
In-Reply-To: <1488671310-27378-1-git-send-email-martin@barkynet.com>

Hello,

On Sat,  4 Mar 2017 23:48:28 +0000, Martin Bark wrote:
> Signed-off-by: Martin Bark <martin@barkynet.com>
> ---
>  DEVELOPERS | 1 +
>  1 file changed, 1 insertion(+)

Applied to master, thanks. I don't remember, did I point you to the bug
https://bugs.busybox.net/show_bug.cgi?id=9531 ? If not, could you have
a look ?

Thanks!

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

  parent reply	other threads:[~2017-03-05 11:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 23:48 [Buildroot] [PATCH 1/3] DEVELOPERS: add Martin Bark for package/nodejs Martin Bark
2017-03-04 23:48 ` [Buildroot] [PATCH 2/3] package/nodejs: bump version to 7.7.1 Martin Bark
2017-03-12 22:36   ` Thomas Petazzoni
2017-03-14  9:11     ` Martin Bark
2017-03-04 23:48 ` [Buildroot] [PATCH 3/3] package/nodejs: remove 0.10.x support Martin Bark
2017-03-05 22:40   ` Arnout Vandecappelle
2017-03-06 10:08     ` Martin Bark
2017-03-06 12:23       ` Arnout Vandecappelle
2017-03-06 21:13         ` Yann E. MORIN
2017-03-07 15:32           ` Peter Korsgaard
2017-03-05 11:13 ` Thomas Petazzoni [this message]
2017-03-05 15:35   ` [Buildroot] [PATCH 1/3] DEVELOPERS: add Martin Bark for package/nodejs Martin Bark
2017-03-05 15:49     ` Yann E. MORIN
2017-03-05 17:51     ` Thomas Petazzoni
2017-03-05 20:28       ` Martin Bark

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=20170305121329.639183c8@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