From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [RFC PATCH proxmox-backup 1/2] pbs-config: use trait object for the backup lock guard
Date: Mon, 6 Sep 2021 12:47:50 +0200 [thread overview]
Message-ID: <05b89644-d4c8-931a-e52d-fa67d0a91b03@proxmox.com> (raw)
In-Reply-To: <645015c1-6a9e-a744-a931-234e4ba1027c@proxmox.com>
[...]
>>
>
> sound ok in general, but then we have to make the field public no ?
> and then we could also open a bug file too, no change in the type needed
> at all... but i thought we want to avoid making the underlying field
> public...
>
>
i meant a 'bogus' file here, not bug...
prev parent reply other threads:[~2021-09-06 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 7:17 Dominik Csapak
2021-09-03 7:17 ` [pbs-devel] [RFC PATCH proxmox-backup 2/2] tape/inventory: fix the tape tests as user by mocking the lock Dominik Csapak
2021-09-06 10:25 ` [pbs-devel] [RFC PATCH proxmox-backup 1/2] pbs-config: use trait object for the backup lock guard Wolfgang Bumiller
2021-09-06 10:41 ` Dominik Csapak
2021-09-06 10:47 ` 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=05b89644-d4c8-931a-e52d-fa67d0a91b03@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pbs-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