From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: [pbs-devel] applied: [PATCH backup 3/3] restore: docs: escape <uid> with code block
Date: Tue, 03 Dec 2024 13:34:01 +0100 [thread overview]
Message-ID: <1733223091.1gly79nm03.astroid@yuna.none> (raw)
In-Reply-To: <20241203093243.97764-3-m.sandoval@proxmox.com>
On December 3, 2024 10:32 am, Maximiliano Sandoval wrote:
> otherwise:
>
> ```
> warning: unclosed HTML tag `uid`
> --> proxmox-file-restore/src/main.rs:686:63
> |
> 686 | /// "www-data", so we use a custom one in /run/proxmox-backup/<uid> instead.
> | ^^^^^
> |
> = note: `#[warn(rustdoc::invalid_html_tags)]` on by default
> ```
there were two more of those that I fixed in the same fashion..
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> proxmox-file-restore/src/main.rs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/proxmox-file-restore/src/main.rs b/proxmox-file-restore/src/main.rs
> index 59ccbe52..572e2d18 100644
> --- a/proxmox-file-restore/src/main.rs
> +++ b/proxmox-file-restore/src/main.rs
> @@ -663,7 +663,7 @@ fn main() {
>
> /// Returns a runtime dir owned by the current user.
> /// Note that XDG_RUNTIME_DIR is not always available, especially for non-login users like
> -/// "www-data", so we use a custom one in /run/proxmox-backup/<uid> instead.
> +/// "www-data", so we use a custom one in `/run/proxmox-backup/<uid>` instead.
> pub fn get_user_run_dir() -> Result<std::path::PathBuf, Error> {
> let uid = nix::unistd::Uid::current();
> let mut path: std::path::PathBuf = pbs_buildcfg::PROXMOX_BACKUP_RUN_DIR.into();
> --
> 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
next prev parent reply other threads:[~2024-12-03 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 9:32 [pbs-devel] [PATCH backup 1/3] client: pxar: docs: do not link to private ExtractorIter struct Maximiliano Sandoval
2024-12-03 9:32 ` [pbs-devel] [PATCH backup 2/3] config: acl: docs: link to PRIVILEGES with namespace Maximiliano Sandoval
2024-12-03 12:34 ` [pbs-devel] applied: " Fabian Grünbichler
2024-12-03 9:32 ` [pbs-devel] [PATCH backup 3/3] restore: docs: escape <uid> with code block Maximiliano Sandoval
2024-12-03 12:34 ` Fabian Grünbichler [this message]
2024-12-03 13:43 ` [pbs-devel] applied: " Maximiliano Sandoval
2024-12-03 12:43 ` [pbs-devel] [PATCH backup 1/3] client: pxar: docs: do not link to private ExtractorIter struct Fabian Grünbichler
2024-12-03 13:44 ` Maximiliano Sandoval
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=1733223091.1gly79nm03.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