From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] DEVELOPERS: add Jörg Krause for augeus
Date: Sat, 11 Feb 2017 16:44:55 +0100 [thread overview]
Message-ID: <20170211164455.64a95639@free-electrons.com> (raw)
In-Reply-To: <20170210110013.30448-2-joerg.krause@embedded.rocks>
Hello,
On Fri, 10 Feb 2017 12:00:13 +0100, J?rg Krause wrote:
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> DEVELOPERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/DEVELOPERS b/DEVELOPERS
> index b8ccb4615..71f9fcad3 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -893,6 +893,7 @@ F: package/x11r7/xdriver_xf86-video-imx/
> F: package/x11r7/xdriver_xf86-video-imx-viv/
>
> N: J?rg Krause <joerg.krause@embedded.rocks>
> +F: package/augeas/
> F: package/bctoolbox/
> F: package/libshout/
> F: package/libupnpp/
We have changed our mind at the last Buildroot developers meeting. We
now want the modification to the DEVELOPERS file to be part of the
patch adding the package. Since you received some feedback on the .mk
file itself, could you resubmit, with the DEVELOPERS changes merged in
the main patch?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-11 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 11:00 [Buildroot] [PATCH 1/2] augeas: new package Jörg Krause
2017-02-10 11:00 ` [Buildroot] [PATCH 2/2] DEVELOPERS: add Jörg Krause for augeus Jörg Krause
2017-02-11 15:44 ` Thomas Petazzoni [this message]
2017-02-13 16:10 ` Jörg Krause
2017-02-11 15:13 ` [Buildroot] [PATCH 1/2] augeas: new package Romain Naour
2017-02-13 16:35 ` Jörg Krause
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=20170211164455.64a95639@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