From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libhtp: bump to version 0.5.38
Date: Fri, 16 Jul 2021 23:33:55 +0200 [thread overview]
Message-ID: <20210716233355.5e255464@windsurf> (raw)
In-Reply-To: <20210702192548.956881-1-fontaine.fabrice@gmail.com>
On Fri, 2 Jul 2021 21:25:47 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> https://github.com/OISF/libhtp/releases/tag/0.5.38
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/libhtp/libhtp.hash | 2 +-
> package/libhtp/libhtp.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Both patches applied, thanks. However, it would have been nice to make
it clear whether the htp bump to 0.5.38 is necessary for the suricata
security bump. Since you sent both in the same series, I assumed it was
the case, but I think it is important to make it clearer in the commit
logs. Indeed, when Peter will review all the commits in "master" to
consider them for the LTS branch, he will see the suricata "security
bump", so he will backport it, but not necessarily that the libhtp bump
is needed together with the suricata bump (if it's the case).
Thanks a lot,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-16 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 19:25 [Buildroot] [PATCH 1/2] package/libhtp: bump to version 0.5.38 Fabrice Fontaine
2021-07-02 19:25 ` [Buildroot] [PATCH 2/2] package/suricata: security bump to version 6.0.3 Fabrice Fontaine
2021-08-03 14:28 ` Peter Korsgaard
2021-07-16 21:33 ` Thomas Petazzoni [this message]
2021-08-03 14:28 ` [Buildroot] [PATCH 1/2] package/libhtp: bump to version 0.5.38 Peter Korsgaard
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=20210716233355.5e255464@windsurf \
--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