From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH stable-7+master manager] pve7to8: fix Ceph noout check
Date: Mon, 17 Jul 2023 14:57:57 +0200 [thread overview]
Message-ID: <693e8857-f1e7-06ee-809a-011686d01efd@proxmox.com> (raw)
In-Reply-To: <20230717083819.25542-1-f.ebner@proxmox.com>
Am 17/07/2023 um 10:38 schrieb Fiona Ebner:
> Commit 114e5f2c ("pve7to8: sync over from stable-7 branch")
> accidentally got rid of the correct value 0 here and also the new TODO
> message to improve the situation. But the TODO is actually easy,
> because there already is the $upgraded variable. Just rely on that
> instead of hard-coding and forgetting about it again.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Should also be applied to stable-7 I guess, so the next sync doesn't
> drop the change again.
>
> PVE/CLI/pve7to8.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
prev parent reply other threads:[~2023-07-17 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 8:38 [pve-devel] " Fiona Ebner
2023-07-17 12:57 ` Thomas Lamprecht [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=693e8857-f1e7-06ee-809a-011686d01efd@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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