From: Aaron Lauterer <a.lauterer@proxmox.com>
To: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH pve-manager] ui: ceph status: add pg warning state
Date: Tue, 8 Aug 2023 09:32:27 +0200 [thread overview]
Message-ID: <fa3b52ce-8196-9af6-17b4-b880101d1c9e@proxmox.com> (raw)
In-Reply-To: <e903ab4f-82b4-4f98-b407-917b68e3bb04@groupe-cyllene.com>
I must have missed them. I'll give them a quick review. Thanks :)
On 8/7/23 09:46, DERUMIER, Alexandre wrote:
> Le 21/07/2023 à 15:08, Aaron Lauterer a écrit :
>> I took the liberty to create a small series of follow up patches to
>> implement the changes I suggested. This should save you, Alexandre,
>> some time. :)
>>
>> I hope that worklow is okay this way.
>>
> Hi,
>
> I'm back from holiday.
>
> I don't known if you had see it, but I have sent patches in June with
> your requested changes:
>
> https://lists.proxmox.com/pipermail/pve-devel/2023-June/057888.html
>
> https://lists.proxmox.com/pipermail/pve-devel/2023-June/057886.html
>
>
>
>
prev parent reply other threads:[~2023-08-08 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 10:54 Alexandre Derumier
2023-06-22 13:50 ` Aaron Lauterer
2023-07-21 13:06 ` [pve-devel] [PATCH widget-toolkit 1/3] css: add 'working' css color class Aaron Lauterer
2023-07-21 13:06 ` [pve-devel] [PATCH manager 2/3] ceph: ui: followup: change blue for PGs in working state Aaron Lauterer
2023-07-21 13:06 ` [pve-devel] [PATCH manager 3/3] ceph: ui: rename PG state error to critical Aaron Lauterer
2023-07-21 13:08 ` [pve-devel] [PATCH pve-manager] ui: ceph status: add pg warning state Aaron Lauterer
2023-08-07 7:46 ` DERUMIER, Alexandre
2023-08-08 7:32 ` Aaron Lauterer [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=fa3b52ce-8196-9af6-17b4-b880101d1c9e@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=Alexandre.DERUMIER@groupe-cyllene.com \
--cc=aderumier@odiso.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.