From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/3] ejabberd: convert patches to git format
Date: Sun, 21 Feb 2016 23:31:01 +0100 [thread overview]
Message-ID: <20160221233101.142f353a@free-electrons.com> (raw)
In-Reply-To: <1456092010-16504-1-git-send-email-fhunleth@troodon-software.com>
Dear Frank Hunleth,
On Sun, 21 Feb 2016 17:00:08 -0500, Frank Hunleth wrote:
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
> ---
> Changes v3 -> v4:
> - Specify -N to git format-patch for patches (suggested by
> Thomas Petazzoni)
All three patches applied to next, thanks.
It would be good if you could talk with upstream to find a solution to
reduce the stack of patches we have against ejabberd.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-21 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 22:00 [Buildroot] [PATCH v4 1/3] ejabberd: convert patches to git format Frank Hunleth
2016-02-21 22:00 ` [Buildroot] [PATCH v4 2/3] ejabberd: bump to version 16.01 Frank Hunleth
2016-02-21 22:00 ` [Buildroot] [PATCH v4 3/3] ejabberd: add reason for autoreconf Frank Hunleth
2016-02-21 22:31 ` Thomas Petazzoni [this message]
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=20160221233101.142f353a@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