From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/4] erlang-p1-xmpp: New package
Date: Wed, 31 May 2017 21:17:41 +0200 [thread overview]
Message-ID: <20170531211741.03e26ae0@free-electrons.com> (raw)
In-Reply-To: <20170531163545.23552-3-johan.oudinet@gmail.com>
Hello,
On Wed, 31 May 2017 18:35:44 +0200, Johan Oudinet wrote:
> XMPP library for Erlang.
> https://github.com/processone/xmpp
>
> Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com>
I've applied to next. However, I have a request for upcoming patches.
> diff --git a/package/erlang-p1-xmpp/0001-fix-includes.patch b/package/erlang-p1-xmpp/0001-fix-includes.patch
> new file mode 100644
> index 0000000000..d0a267b721
> --- /dev/null
> +++ b/package/erlang-p1-xmpp/0001-fix-includes.patch
> @@ -0,0 +1,16 @@
> +Without this patch, rebar fails to find include file fxml.hrl.
> +
> +Signed-off-by: Christophe Romain <cromain@process-one.net>
Since all those packages are hosted in Git repository, we would very
much prefer to have patches created with "git format-patch", as they
can more easily be applied using "git am".
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-31 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 16:35 [Buildroot] [PATCH v2 1/4] erlang-jiffy: New package Johan Oudinet
2017-05-31 16:35 ` [Buildroot] [PATCH v2 2/4] erlang-p1-oauth2: " Johan Oudinet
2017-05-31 19:15 ` Thomas Petazzoni
2017-05-31 16:35 ` [Buildroot] [PATCH v2 3/4] erlang-p1-xmpp: " Johan Oudinet
2017-05-31 19:17 ` Thomas Petazzoni [this message]
2017-05-31 16:35 ` [Buildroot] [PATCH v2 4/4] ejabberd: bump to version 17.04 Johan Oudinet
2017-05-31 19:18 ` Thomas Petazzoni
2017-05-31 19:15 ` [Buildroot] [PATCH v2 1/4] erlang-jiffy: New package 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=20170531211741.03e26ae0@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