From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Stefan Sterz <s.sterz@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup 1/2] docs: minor re-phrasing and spell checking clean up
Date: Mon, 28 Nov 2022 16:03:53 +0100 [thread overview]
Message-ID: <3491e654-62c3-f9f2-55cd-8efec8ccbf82@proxmox.com> (raw)
In-Reply-To: <20221128143401.610254-1-s.sterz@proxmox.com>
Am 28/11/2022 um 15:34 schrieb Stefan Sterz:
> Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
> ---
> docs/storage.rst | 37 +++++++++++++++++++------------------
> 1 file changed, 19 insertions(+), 18 deletions(-)
>
>
applied both patches and removed the extra 'd' Daniel spotted in a follow up,
thanks to both of you!
prev parent reply other threads:[~2022-11-28 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 14:34 [pbs-devel] " Stefan Sterz
2022-11-28 14:34 ` [pbs-devel] [PATCH proxmox-backup 2/2] docs: add paragraph on verification jobs to ransomware section Stefan Sterz
2022-11-28 14:52 ` [pbs-devel] [PATCH proxmox-backup 1/2] docs: minor re-phrasing and spell checking clean up Daniel Tschlatscher
2022-11-28 15:03 ` 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=3491e654-62c3-f9f2-55cd-8efec8ccbf82@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.sterz@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