From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: applied: [PATCH log-tracker v2 1/3] split out pmg-smtp-filter qid parsing
Date: Wed, 17 Jun 2026 13:51:46 +0200 [thread overview]
Message-ID: <178169700491.30353.9624843726718278475.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260617074934.955079-1-d.csapak@proxmox.com>
Thanks for the quick iteration on this and the explanations on my
comments!
Gave it another look, ran some more benchmarks on some live syslogs, and
additionally compared the (sorted) output with your patch and without with
those logs - looked ok.
On Wed, 17 Jun 2026 09:47:48 +0200, Dominik Csapak wrote:
> By splitting out the parsing of the pmg-smtp-filter QIDs, we can more
> rigorously parse them since the parser does not have to overlap with
> postfix's QIDs'. We have a bit of code duplication, but more clarity
> when reading the code and better checks.
>
> Since we know how long the pmg-smtp-filter QIDs must be, we can also
> filter by the length.
>
> [...]
Applied, thanks!
[1/3] split out pmg-smtp-filter qid parsing
commit: e90400ddadb396197a5b677109c86d5681a75e64
[2/3] parse_qid{_prefix}: remove 'max' parameter
commit: 129d533dedff1a554c04fa3c113564c23df98415
[3/3] fix #7702: improve postfix QID parsing
commit: 83c77b7da75bf9e9d41c3526401c9a2024ad0c60
prev parent reply other threads:[~2026-06-17 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 7:47 [PATCH log-tracker v2 1/3] split out pmg-smtp-filter qid parsing Dominik Csapak
2026-06-17 7:47 ` [PATCH log-tracker v2 2/3] parse_qid{_prefix}: remove 'max' parameter Dominik Csapak
2026-06-17 7:47 ` [PATCH log-tracker v2 3/3] fix #7702: improve postfix QID parsing Dominik Csapak
2026-06-17 11:51 ` Stoiko Ivanov [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=178169700491.30353.9624843726718278475.b4-ty@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=d.csapak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.