From: Lukas Wagner <l.wagner@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [PATCH datacenter-manager] move developer-facing documentation to top-level 'dev-docs' dir
Date: Wed, 25 Mar 2026 13:51:52 +0100 [thread overview]
Message-ID: <20260325125152.245079-1-l.wagner@proxmox.com> (raw)
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.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
docs/dev/debug-features.md => dev-docs/fake-remotes.md | 4 +---
{docs/dev => dev-docs}/pdm-permission-system.md | 0
2 files changed, 1 insertion(+), 3 deletions(-)
rename docs/dev/debug-features.md => dev-docs/fake-remotes.md (94%)
rename {docs/dev => dev-docs}/pdm-permission-system.md (100%)
diff --git a/docs/dev/debug-features.md b/dev-docs/fake-remotes.md
similarity index 94%
rename from docs/dev/debug-features.md
rename to dev-docs/fake-remotes.md
index 26daecb5..7937525d 100644
--- a/docs/dev/debug-features.md
+++ b/dev-docs/fake-remotes.md
@@ -1,6 +1,4 @@
-# Debug features
-
-## Faked remotes
+# Faked remotes
To enable an alternative implementation for reading remote configurations (`/etc/proxmox-datacenter-manager/remotes.cfg`)
and creating API clients for these remotes, compile the project using:
diff --git a/docs/dev/pdm-permission-system.md b/dev-docs/pdm-permission-system.md
similarity index 100%
rename from docs/dev/pdm-permission-system.md
rename to dev-docs/pdm-permission-system.md
--
2.47.3
next reply other threads:[~2026-03-25 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:51 Lukas Wagner [this message]
2026-03-25 16:55 ` 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=20260325125152.245079-1-l.wagner@proxmox.com \
--to=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