From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] pbs-config: fix unresolved link warnings by correcting the links
Date: Mon, 17 Mar 2025 13:55:04 +0100 [thread overview]
Message-ID: <1742215931.7t6ehcocj1.astroid@yuna.none> (raw)
In-Reply-To: <20250312110011.115684-1-s.sterz@proxmox.com>
On March 12, 2025 12:00 pm, Shannon Sterz wrote:
> otherwise creating the docs for pbs-config throws a warning
>
> Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
> ---
> pbs-config/src/drive.rs | 8 ++++----
> pbs-config/src/media_pool.rs | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/pbs-config/src/drive.rs b/pbs-config/src/drive.rs
> index 4e2befd2..a833fc8e 100644
> --- a/pbs-config/src/drive.rs
> +++ b/pbs-config/src/drive.rs
> @@ -6,10 +6,10 @@
> //!
> //! Drive type [`VirtualTapeDrive`] is only useful for debugging.
> //!
> -//! [LtoTapeDrive]: crate::api2::types::LtoTapeDrive
> -//! [VirtualTapeDrive]: crate::api2::types::VirtualTapeDrive
> -//! [ScsiTapeChanger]: crate::api2::types::ScsiTapeChanger
> -//! [SectionConfig]: proxmox::api::section_config::SectionConfig
> +//! [LtoTapeDrive]: pbs_api_types::LtoTapeDrive
> +//! [VirtualTapeDrive]: pbs_api_types::VirtualTapeDrive
> +//! [ScsiTapeChanger]: pbs_api_types::ScsiTapeChanger
> +//! [SectionConfig]: proxmox_section_config::SectionConfig
>
> use std::collections::HashMap;
> use std::sync::LazyLock;
> diff --git a/pbs-config/src/media_pool.rs b/pbs-config/src/media_pool.rs
> index 3bf15188..7ee91c44 100644
> --- a/pbs-config/src/media_pool.rs
> +++ b/pbs-config/src/media_pool.rs
> @@ -3,7 +3,7 @@
> //! This configuration module is based on [`SectionConfig`], and
> //! provides a type safe interface to store [`MediaPoolConfig`],
> //!
> -//! [MediaPoolConfig]: crate::api2::types::MediaPoolConfig
> +//! [MediaPoolConfig]: pbs_api_types::MediaPoolConfig
> //! [SectionConfig]: proxmox_section_config::SectionConfig
>
> use std::collections::HashMap;
> --
> 2.39.5
>
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>
>
>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-03-17 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 11:00 [pbs-devel] " Shannon Sterz
2025-03-17 12:55 ` Fabian Grünbichler [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=1742215931.7t6ehcocj1.astroid@yuna.none \
--to=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal