public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Oguz Bektas <o.bektas@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	pve-devel@pve.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-docs 2/3] ha-manager: fix typos and grammatical errors; improve wording
Date: Wed, 15 Jul 2020 18:44:26 +0200	[thread overview]
Message-ID: <494387cd-067a-73cd-950e-3119d45d19a4@proxmox.com> (raw)
In-Reply-To: <20200715150737.GA13999@gaia.proxmox.com>

On 15.07.20 17:07, Oguz Bektas wrote:
>> +Last but not least, you can also manually move resources to other nodes, before
> better without comma s/nodes,/nodes/

would that be wrong then, the comma is OK here, AFAICT.




      reply	other threads:[~2020-07-15 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 14:28 Dylan Whyte
2020-07-15 15:07 ` Oguz Bektas
2020-07-15 16:44   ` 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=494387cd-067a-73cd-950e-3119d45d19a4@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=o.bektas@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=pve-devel@pve.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal