From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] clamav: reformat patches as Git-formatted patches
Date: Sun, 13 May 2018 23:00:14 +0200 [thread overview]
Message-ID: <20180513230014.29febbe2@windsurf.home> (raw)
In-Reply-To: <20180507212031.31337-1-thomas.petazzoni@bootlin.com>
Hello,
On Mon, 7 May 2018 23:20:30 +0200, Thomas Petazzoni wrote:
> ClamAV is using Git upstream
> (https://github.com/Cisco-Talos/clamav-devel), so it makes sense to
> use Git-formatted patches.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> ...roto.c-fix-build-error-due-to-missing-soc.patch | 34 ++++++++++++++++++++++
> package/clamav/0001-clamdscan.patch | 21 -------------
> ...use-backtrace-if-using-uClibc-without-ba.patch} | 22 ++++++++++----
> 3 files changed, 51 insertions(+), 26 deletions(-)
> create mode 100644 package/clamav/0001-clamdscan-proto.c-fix-build-error-due-to-missing-soc.patch
> delete mode 100644 package/clamav/0001-clamdscan.patch
> rename package/clamav/{0002-backtrace-uClibc.patch => 0002-mbox-do-not-use-backtrace-if-using-uClibc-without-ba.patch} (53%)
Thanks to Yann's review, both patches have been applied to master.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-13 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 21:20 [Buildroot] [PATCH 1/2] clamav: reformat patches as Git-formatted patches Thomas Petazzoni
2018-05-07 21:20 ` [Buildroot] [PATCH 2/2] clamav: add patch to fix build failure caused by lack of libcurl Thomas Petazzoni
2018-05-13 20:48 ` Yann E. MORIN
2018-05-13 20:44 ` [Buildroot] [PATCH 1/2] clamav: reformat patches as Git-formatted patches Yann E. MORIN
2018-05-13 21:00 ` 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=20180513230014.29febbe2@windsurf.home \
--to=thomas.petazzoni@bootlin.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