From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Mario Loderer <m.loderer@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] qm: fix formula for ballooning
Date: Thu, 4 Jul 2024 15:31:40 +0200 [thread overview]
Message-ID: <14d71a92-069d-4d46-a561-bb0b5d192da2@proxmox.com> (raw)
In-Reply-To: <20240704132640.154557-1-m.loderer@proxmox.com>
On 2024-07-04 15:26, Mario Loderer wrote:
> move "+" in to new line, if it set at the end of the line it will be
> lost
>
> Signed-off-by: Mario Loderer <m.loderer@proxmox.com>
> ---
> qm.adoc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
applied with a small addition to the commit message to make it clear
where the plus is lost, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-04 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 13:26 [pve-devel] " Mario Loderer
2024-07-04 13:31 ` Aaron Lauterer [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=14d71a92-069d-4d46-a561-bb0b5d192da2@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=m.loderer@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