From: "Shan Shaji" <s.shaji@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>,
"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve_flutter_frontend] fix: ui: remove blue background under bottom bar in iOS
Date: Tue, 10 Jun 2025 17:49:06 +0200 [thread overview]
Message-ID: <DAIYZXH7YQY9.2C2M48SSK92N2@noor> (raw)
In-Reply-To: <e3c7ae89-2132-42e7-ac30-040564c24e7b@proxmox.com>
Thank you for the review. Will send another updated patch.
On Tue Jun 10, 2025 at 5:31 PM CEST, Michael Köppl wrote:
> Due to the changes to _MobileResourceFilterSheet [0], this patch no
> longer applies. Needs a rebase.
>
> [0]
> https://lore.proxmox.com/pve-devel/20250522130825.79862-1-s.shaji@proxmox.com/
_______________________________________________
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:[~2025-06-10 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 11:32 Shan Shaji
2025-06-10 15:31 ` Michael Köppl
2025-06-10 15:49 ` Shan Shaji [this message]
2025-06-12 9:03 ` Shan Shaji
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=DAIYZXH7YQY9.2C2M48SSK92N2@noor \
--to=s.shaji@proxmox.com \
--cc=m.koeppl@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