From: Dominik Csapak <d.csapak@proxmox.com>
To: Stefan Reiter <s.reiter@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/2] proxy: fix error handling in prune scheduling
Date: Thu, 24 Sep 2020 16:04:01 +0200 [thread overview]
Message-ID: <86c520ad-9b1d-1ab4-8b1f-0a8e38a2a6c8@proxmox.com> (raw)
In-Reply-To: <b15afe05-9a85-6ff7-1f6f-482330fff275@proxmox.com>
On 9/24/20 4:01 PM, Stefan Reiter wrote:
> Don't we also have the proxmox::try_block! macro? What's the difference
> to that then?
ah yes, you're right. i missed that this exists^^
i'll send a v2 for both patches using the try_block! macro
prev parent reply other threads:[~2020-09-24 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 13:52 Dominik Csapak
2020-09-24 13:52 ` [pbs-devel] [PATCH proxmox-backup 2/2] use jobstate mechanism for verify/garbage_collection schedules Dominik Csapak
2020-09-24 14:01 ` [pbs-devel] [PATCH proxmox-backup 1/2] proxy: fix error handling in prune scheduling Stefan Reiter
2020-09-24 14:04 ` Dominik Csapak [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=86c520ad-9b1d-1ab4-8b1f-0a8e38a2a6c8@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.reiter@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