From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] package-repos: fix disabling deb822 repository instructions
Date: Fri, 19 Sep 2025 09:40:34 +0200 [thread overview]
Message-ID: <175826763302.2062176.12150237562503488303.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250918184850.2808572-1-s.ivanov@proxmox.com>
On Thu, 18 Sep 2025 20:48:50 +0200, Stoiko Ivanov wrote:
> noticed this and the missing full-stop while carrying over the
> changes to pmg-docs.
>
>
Applied, thanks! There was a duplicate "of" and sources.list uses the "Enabled:
no" variant, so I reworded it a bit in a follow up.
[1/1] package-repos: fix disabling deb822 repository instructions
commit: a44a78ae46417256f402ef33a8aceadb54daa247
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-19 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 18:48 [pve-devel] " Stoiko Ivanov
2025-09-19 7:40 ` Thomas Lamprecht [this message]
2025-09-19 8:18 ` [pve-devel] applied: " Stoiko Ivanov
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=175826763302.2062176.12150237562503488303.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-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