From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Folke Gleumes <f.gleumes@proxmox.com>
Subject: [pve-devel] applied: [PATCH common] docs: add missing prefix
Date: Mon, 8 Apr 2024 18:01:58 +0200 [thread overview]
Message-ID: <734feed0-a4aa-426c-9a7d-48bde534b025@proxmox.com> (raw)
In-Reply-To: <20240327130922.246799-1-f.gleumes@proxmox.com>
Am 27/03/2024 um 14:09 schrieb Folke Gleumes:
> include 'PVEAPIToken=' prefix in the example for target-endpoint which
> is mainly used for remote migrations.
>
> Signed-off-by: Folke Gleumes <f.gleumes@proxmox.com>
> ---
> src/PVE/JSONSchema.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
prev parent reply other threads:[~2024-04-08 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 13:09 [pve-devel] " Folke Gleumes
2024-04-08 16:01 ` 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=734feed0-a4aa-426c-9a7d-48bde534b025@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gleumes@proxmox.com \
--cc=pve-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