From: Robert Obkircher <r.obkircher@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container/docs/manager 0/3] document that systemd requires LXC nesting
Date: Wed, 22 Oct 2025 12:03:39 +0200 [thread overview]
Message-ID: <20251022100937.25762-1-r.obkircher@proxmox.com> (raw)
Updates docs and API schema.
The new onlineHelp link is not ideal, because it requires scrolling
down a bit to the features section of the options. Would it make sense
to make it possible to link there directly?
pve-docs:
Robert Obkircher (1):
fix #6897: document that systemd requires LXC nesting
pct.adoc | 1 +
1 file changed, 1 insertion(+)
pve-container:
Robert Obkircher (1):
fix #6897: document that systemd requires nesting
src/PVE/LXC/Config.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
pve-manager:
Robert Obkircher (1):
fix #6897: ui: add onlineHelp to lxc/FeaturesEdit
www/manager6/lxc/FeaturesEdit.js | 1 +
1 file changed, 1 insertion(+)
Summary over all repositories:
3 files changed, 3 insertions(+), 1 deletions(-)
--
Generated by git-murpp 0.8.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-10-22 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 10:03 Robert Obkircher [this message]
2025-10-22 10:03 ` [pve-devel] [PATCH pve-docs 1/1] fix #6897: " Robert Obkircher
2025-10-22 11:37 ` Shannon Sterz
2025-10-23 13:51 ` [pve-devel] applied: " Thomas Lamprecht
2025-10-22 10:03 ` [pve-devel] [PATCH pve-container 1/1] fix #6897: document that systemd requires nesting Robert Obkircher
2025-10-22 11:37 ` Shannon Sterz
2025-10-22 10:03 ` [pve-devel] [PATCH pve-manager 1/1] fix #6897: ui: add onlineHelp to lxc/FeaturesEdit Robert Obkircher
2025-10-22 11:37 ` Shannon Sterz
2025-10-23 14:44 ` [pve-devel] applied: " Thomas Lamprecht
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=20251022100937.25762-1-r.obkircher@proxmox.com \
--to=r.obkircher@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