From: Noel Ullreich <n.ullreich@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH proxmox-backup/docs 2/2] Fixed spelling of command line/command-line
Date: Mon, 3 Jul 2023 10:15:09 +0200 [thread overview]
Message-ID: <b5014dc6-9c4d-e9a7-2cf6-572248bc0dc9@proxmox.com> (raw)
In-Reply-To: <c656ca81-9107-963b-7aa3-58bce900ee6d@proxmox.com>
Whoops, thank you.
Not a good look to correct spelling and then having a bunch of spelling
mistakes in the "correction". I guess I should probs install a vim
spellchecker :P
On 27-06-2023 15:50, Thomas Lamprecht wrote:
> Am 27/06/2023 um 14:40 schrieb Noel Ullreich:
>> Commandline/command line/command-line where being used interchangably,
>> which is not correct
>> (see: https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/command-line).
>> use command-line when it is an adjective (e.g. "command-line interface")
>> and use command line when it is a noun (e.g. "change the setting from
>> the command line")
>>
>> Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
>> ---
>> docs/backup-client.rst | 6 +++---
>> docs/certificate-management.rst | 8 ++++----
>> docs/command-line-tools.rst | 2 +-
>> docs/command-syntax.rst | 2 +-
>> docs/introduction.rst | 2 +-
>> docs/network-management.rst | 4 ++--
>> docs/package-repositories.rst | 2 +-
>> docs/proxmox-file-restore/description.rst | 2 +-
>> docs/pve-integration.rst | 2 +-
>> docs/pxar-tool.rst | 2 +-
>> docs/pxar/description.rst | 2 +-
>> docs/tape-backup.rst | 8 ++++----
>> docs/technical-overview.rst | 2 +-
>> docs/user-management.rst | 2 +-
>> 14 files changed, 23 insertions(+), 23 deletions(-)
>>
>>
> applied, fixed a few typos (s/where/were;s/interchangably/interchangeably/)
> in the commit message, also changed the subject to imperative, as mentioned
> already in the past, you "fix" something with this commit (otherwise it would
> need time travel ;-) - also this would belong to the pbs-devel list.
next prev parent reply other threads:[~2023-07-03 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 12:40 [pve-devel] [PATCH pmg-docs; pmg-docs; proxmox-backup/docs 0/8] fix consistency of some words Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pve-docs 1/4] consistency of passthrough/pass-through Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pve-docs 2/4] consistency: change mainboard to motherboard Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pve-docs 3/4] consistenct of USB flash drive spelling Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pve-docs 4/4] Fixed spelling of command line/command-line Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH proxmox-backup/docs 1/2] consistenct of USB flash drive spelling Noel Ullreich
2023-06-27 13:45 ` [pve-devel] applied: " Thomas Lamprecht
2023-06-27 12:40 ` [pve-devel] [PATCH proxmox-backup/docs 2/2] Fixed spelling of command line/command-line Noel Ullreich
2023-06-27 13:50 ` [pve-devel] applied: " Thomas Lamprecht
2023-07-03 8:15 ` Noel Ullreich [this message]
2023-06-27 12:40 ` [pve-devel] [PATCH pmg-docs 1/2] consistenct of USB flash drive spelling Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pmg-docs 2/2] Fixed spelling of command line/command-line Noel Ullreich
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=b5014dc6-9c4d-e9a7-2cf6-572248bc0dc9@proxmox.com \
--to=n.ullreich@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