From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pdm-devel@lists.proxmox.com, Lukas Wagner <l.wagner@proxmox.com>
Subject: applied: [PATCH datacenter-manager] move developer-facing documentation to top-level 'dev-docs' dir
Date: Wed, 25 Mar 2026 17:55:16 +0100 [thread overview]
Message-ID: <177445770876.3365226.5638818007070902577.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260325125152.245079-1-l.wagner@proxmox.com>
On Wed, 25 Mar 2026 13:51:52 +0100, Lukas Wagner wrote:
> The 'docs/dev' subfolder is quite easy to miss, so I think it makes
> sense increase the visibility of the (sparse) developer documentation by
> promoting it to a top-level directory.
>
>
Applied, thanks!
[1/1] move developer-facing documentation to top-level 'dev-docs' dir
commit: ca72e698c815c33167a5efc49c1fe7d181da4151
prev parent reply other threads:[~2026-03-25 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:51 Lukas Wagner
2026-03-25 16:55 ` 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=177445770876.3365226.5638818007070902577.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pdm-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