From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pdm-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pdm-devel] [RFC proxmox-datacenter-manager] docs: roadmap: group similar entries and minor fixups
Date: Wed, 3 Dec 2025 20:46:30 +0100 [thread overview]
Message-ID: <176479118707.2366933.9760290202099608853.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251203193753.2672751-1-s.ivanov@proxmox.com>
On Wed, 03 Dec 2025 20:35:24 +0100, Stoiko Ivanov wrote:
> While reading through the roadmap I felt that some items belong
> together under a separate heading (improved docs and support for
> subscription management in the UI and support for PBS remotes in the
> backend).
>
> Additionally dropped an item with little information for me (fix
> various typos)
>
> [...]
Applied, thanks!
[1/1] docs: roadmap: group similar entries and minor fixups
commit: ac0f346e02eff9f1d74866aaf689bb06f7fce904
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
prev parent reply other threads:[~2025-12-03 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 19:35 Stoiko Ivanov
2025-12-03 19:46 ` 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=176479118707.2366933.9760290202099608853.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.ivanov@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