From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christoph Heiss <c.heiss@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup 0/2] docs: network-management: improve pinning docs a bit
Date: Mon, 15 Sep 2025 22:10:04 +0200 [thread overview]
Message-ID: <175796695405.463585.8971453196333165100.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250812125719.1301475-1-c.heiss@proxmox.com>
On Tue, 12 Aug 2025 14:57:16 +0200, Christoph Heiss wrote:
> First patch fixes the codeblock syntax of the section, as it uses the
> asciidoc one rather than the RestructuredText, causing wrong rendering
> in the final documentation.
>
> Second patch just adds a link to the systemd .link file documentation,
> as that might be useful to users to have directly available.
>
> [...]
Applied, thanks!
[1/2] docs: network-management: use correct syntax for code-blocks
commit: 1da0b868f66a1a4263922057cc2f12178b244cb4
[2/2] docs: network-management: link to systemd.link documentation
commit: 832664ffcf60785a40bfa16da3a667da9bdf8b6d
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-09-15 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:57 [pbs-devel] [PATCH proxmox-backup 0/2] docs: network-management: improve pinning docs a bit Christoph Heiss
2025-08-12 12:57 ` [pbs-devel] [PATCH proxmox-backup 1/2] docs: network-management: use correct syntax for code-blocks Christoph Heiss
2025-08-12 12:57 ` [pbs-devel] [PATCH proxmox-backup 2/2] docs: network-management: link to systemd.link documentation Christoph Heiss
2025-08-12 13:48 ` [pbs-devel] [PATCH proxmox-backup 0/2] docs: network-management: improve pinning docs a bit Michael Köppl
2025-09-15 20:10 ` 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=175796695405.463585.8971453196333165100.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=pbs-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