From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-api 0/2] upgrade related bugfixes and improvements
Date: Wed, 30 Jun 2021 18:39:53 +0200 [thread overview]
Message-ID: <20210630163955.18639-1-s.ivanov@proxmox.com> (raw)
The 2 patches are independent of each other, but were both reported
by Martin, after he attempted an upgrade to Bullseye:
* sending the first one, since I introduced it, being convinced that such a
small change would not need reviewing
* the change for the ClamAV defaults also makes sense (although just now
clamav seems to have a problem with incremental downloads ...)
Stoiko Ivanov (2):
utils: fix service_aliases usage
config: freshclam: default to incremental downloads
src/PMG/Config.pm | 2 +-
src/PMG/Utils.pm | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2021-06-30 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 16:39 Stoiko Ivanov [this message]
2021-06-30 16:39 ` [pmg-devel] [PATCH pmg-api 1/2] utils: fix service_aliases usage Stoiko Ivanov
2021-06-30 16:39 ` [pmg-devel] [PATCH pmg-api 2/2] config: freshclam: default to incremental downloads Stoiko Ivanov
2021-07-05 6:34 ` [pmg-devel] applied-series: [PATCH pmg-api 0/2] upgrade related bugfixes and improvements Thomas Lamprecht
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=20210630163955.18639-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
/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