From: Noel Ullreich <n.ullreich@proxmox.com>
To: pbs-devel@lists.proxmox.com
Cc: Noel Ullreich <nullreich@eloa.proxmox.com>,
Noel Ullreich <n.ullreich@proxmox.com>
Subject: [pbs-devel] [PATCH proxmox-backup 1/5] readme: fixed typo in readme
Date: Wed, 23 Nov 2022 18:48:06 +0100 [thread overview]
Message-ID: <20221123174810.2703466-2-n.ullreich@proxmox.com> (raw)
In-Reply-To: <20221123174810.2703466-1-n.ullreich@proxmox.com>
From: Noel Ullreich <nullreich@eloa.proxmox.com>
fixed a typo in the readme because i am a huge pedant
Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
---
README.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.rst b/README.rst
index 53f53e42..934c49ec 100644
--- a/README.rst
+++ b/README.rst
@@ -65,7 +65,7 @@ You are now able to build using the Makefile or cargo itself, e.g.::
Design Notes
************
-Here are some random thought about the software design (unless I find a better place).
+Here are some random thoughts about the software design (unless I find a better place).
Large chunk sizes
--
2.30.2
next prev parent reply other threads:[~2022-11-23 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 17:48 [pbs-devel] [PATCH proxmox-backup 0/5] added section on ransomware to docs Noel Ullreich
2022-11-23 17:48 ` Noel Ullreich [this message]
2022-11-24 9:09 ` [pbs-devel] [PATCH proxmox-backup 1/5] readme: fixed typo in readme Thomas Lamprecht
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 2/5] docs: changed wording Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 3/5] docs: fixed capitalization Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 4/5] docs: main features ransomware Noel Ullreich
2022-11-24 9:35 ` Thomas Lamprecht
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 5/5] docs: added section on ransomware Noel Ullreich
2022-11-24 10:23 ` Thomas Lamprecht
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=20221123174810.2703466-2-n.ullreich@proxmox.com \
--to=n.ullreich@proxmox.com \
--cc=nullreich@eloa.proxmox.com \
--cc=pbs-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