From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH backup-qemu] make capi_types module public
Date: Wed, 13 Mar 2024 14:39:36 +0100 [thread overview]
Message-ID: <20240313133936.108667-1-f.schauer@proxmox.com> (raw)
Commit c7077bb3 moved ProxmoxBackupHandle into a separate file and
accidentally made it private in the process.
Revert this behaviour by making ProxmoxBackupHandle and
ProxmoxRestoreHandle accessible from outside of the crate again. These
handles are used in the function signatures of several public functions,
therefore it makes sense to have them public as well.
Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
---
src/lib.rs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/lib.rs b/src/lib.rs
index 02e74f7..9067fc5 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -11,7 +11,7 @@ use proxmox_lang::try_block;
use pbs_api_types::{Authid, BackupDir, BackupNamespace, BackupType, CryptMode};
use pbs_client::BackupRepository;
-mod capi_types;
+pub mod capi_types;
use capi_types::*;
mod commands;
--
2.39.2
next reply other threads:[~2024-03-13 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 13:39 Filip Schauer [this message]
2024-04-09 8:51 ` [pve-devel] applied: " Wolfgang Bumiller
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=20240313133936.108667-1-f.schauer@proxmox.com \
--to=f.schauer@proxmox.com \
--cc=pve-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