From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/clamav: security bump version to 1.0.4
Date: Wed, 01 Nov 2023 10:06:05 +0100 [thread overview]
Message-ID: <87pm0tzvuq.fsf@48ers.dk> (raw)
In-Reply-To: <20231026173442.4149220-1-bernd@kuhls.net> (Bernd Kuhls's message of "Thu, 26 Oct 2023 19:34:42 +0200")
>>>>> "Bernd" == Bernd Kuhls <bernd@kuhls.net> writes:
> Release notes:
> https://blog.clamav.net/2023/10/clamav-121-113-104-010311-patch.html
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Committed to 2023.08.x, thanks.
For 2023.02.x I will instead bump to 0.103.11, which contains the same
fixes.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-01 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 17:34 [Buildroot] [PATCH 1/1] package/clamav: security bump version to 1.0.4 Bernd Kuhls
2023-10-29 8:47 ` Yann E. MORIN
2023-11-01 9:06 ` Peter Korsgaard [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=87pm0tzvuq.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
/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