From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: applied: [pve-devel] [PATCH container] config: document that nameserver is a list
Date: Sat, 7 Nov 2026 19:01:14 +0100 [thread overview]
Message-ID: <179407275613.1575726.687466445973966691.b4-ty@b4> (raw)
In-Reply-To: <20251218151944.869104-1-m.sandoval@proxmox.com>
On Thu, 18 Dec 2025 16:19:41 +0100, Maximiliano Sandoval wrote:
> And for good measure, mention that it is comma-separated (even though it
> can also be space-separated).
Applied, thanks!
[1/1] config: document that nameserver is a list
commit: 287d65393cad84c98085fd23d544fefb3158be31
prev parent reply other threads:[~2026-11-07 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 15:19 [pve-devel] [PATCH container] config: document that nameserver is a list Maximiliano Sandoval
2026-01-15 13:16 ` Fabian Grünbichler
2026-11-07 18:01 ` 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=179407275613.1575726.687466445973966691.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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