From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH proxmox-perl-rs] pve-rs: pmg-rs: move deprecated .cargo/config to .cargo/config.toml
Date: Thu, 20 Jun 2024 11:04:36 +0200 [thread overview]
Message-ID: <23993bde-2c9f-45f0-ab4b-c3e026c00e2b@proxmox.com> (raw)
In-Reply-To: <20240620085911.111673-1-l.wagner@proxmox.com>
Whoops, seems like I was on stable rust (1.78) and the warning only appears there
but not on 1.77 (packaged rust) - but we can apply that already anyway,
saves us the trouble once we are on 1.78 :)
On 2024-06-20 10:59, Lukas Wagner wrote:
> Fixes the following new warning that appeared after switching
> to rust 1.77:
>
> warning: `proxmox-perl-rs/pve-rs/.cargo/config` is deprecated in
> favor of `config.toml`
>
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> ---
> pmg-rs/.cargo/{config => config.toml} | 0
> pve-rs/.cargo/{config => config.toml} | 0
> 2 files changed, 0 insertions(+), 0 deletions(-)
> rename pmg-rs/.cargo/{config => config.toml} (100%)
> rename pve-rs/.cargo/{config => config.toml} (100%)
>
> diff --git a/pmg-rs/.cargo/config b/pmg-rs/.cargo/config.toml
> similarity index 100%
> rename from pmg-rs/.cargo/config
> rename to pmg-rs/.cargo/config.toml
> diff --git a/pve-rs/.cargo/config b/pve-rs/.cargo/config.toml
> similarity index 100%
> rename from pve-rs/.cargo/config
> rename to pve-rs/.cargo/config.toml
--
- Lukas
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-06-20 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 8:59 Lukas Wagner
2024-06-20 9:04 ` Lukas Wagner [this message]
2024-06-20 10:21 ` [pve-devel] applied: " Fabian Grünbichler
2024-06-20 10:41 ` Lukas Wagner
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=23993bde-2c9f-45f0-ab4b-c3e026c00e2b@proxmox.com \
--to=l.wagner@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