From: Friedrich Weber <f.weber@proxmox.com>
To: Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH container] lxc start: warn in case of conflicting lxc.idmap entries
Date: Fri, 17 Mar 2023 09:53:08 +0100 [thread overview]
Message-ID: <96ec7232-0c5c-bb91-04c4-d92b8bfd5eb0@proxmox.com> (raw)
In-Reply-To: <20230316160943.n4ys2xfuyl3tl2ii@casey.proxmox.com>
On 16/03/2023 17:09, Wolfgang Bumiller wrote:
> Since it's about helping out users, even better would be to collect all
> the errors together and than die() with a message containing all of
> them.
> And then the order doesn't matter again ;-)
Agree. :) So I'll prepare a v2 that
* is based on the sorting approach you suggested
* reports all errors to the user (hopefully without being too verbose)
* and probably removes the weird "<100 entries" limitation
prev parent reply other threads:[~2023-03-17 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 17:03 Friedrich Weber
2023-03-16 13:59 ` Wolfgang Bumiller
2023-03-16 15:07 ` Friedrich Weber
2023-03-16 16:09 ` Wolfgang Bumiller
2023-03-17 8:53 ` Friedrich Weber [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=96ec7232-0c5c-bb91-04c4-d92b8bfd5eb0@proxmox.com \
--to=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@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