From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Robert Obkircher <r.obkircher@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 pve-container 0/1] document that systemd requires nesting
Date: Mon, 27 Oct 2025 15:06:20 +0100 [thread overview]
Message-ID: <176157397919.3803610.12365425945610864886.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251024090436.12737-1-r.obkircher@proxmox.com>
On Fri, 24 Oct 2025 11:03:36 +0200, Robert Obkircher wrote:
> Changes since v1:
> - applied nit from Shannons review
>
> Robert Obkircher (1):
> fix #6897: document that systemd requires nesting
>
> src/PVE/LXC/Config.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> [...]
Applied, thanks!
[1/1] fix #6897: document that systemd requires nesting
commit: baae8c74452020f12d3da4fd0376e5c2e8a3ca3a
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-10-27 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 9:03 [pve-devel] " Robert Obkircher
2025-10-24 9:03 ` [pve-devel] [PATCH v2 pve-container 1/1] fix #6897: " Robert Obkircher
2025-10-27 14:06 ` 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=176157397919.3803610.12365425945610864886.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=r.obkircher@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.