From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Kefu Chai <k.chai@proxmox.com>
Subject: applied: [PATCH docs 0/4] ceph: audit of Ceph-related chapters
Date: Thu, 30 Apr 2026 13:28:55 +0200 [thread overview]
Message-ID: <177754853204.1242101.10501126077373084159.b4-ty@b4> (raw)
In-Reply-To: <20260411125036.778122-1-k.chai@proxmox.com>
On Sat, 11 Apr 2026 20:50:32 +0800, Kefu Chai wrote:
> Collected fixes found during a proofreading pass of the Ceph-related
> chapters. 1/4 and 2/4 fix technical inaccuracies; 3/4 and 4/4 are
> small language fixes. See the commit descriptions.
>
> Kefu Chai (4):
> pveceph: fix Ceph Manager abbreviation
> pve-storage-cephfs: describe CephFS, not RBD, in external cluster
> setup
> pveceph: various small language fixes
> docs: various small grammar fixes
>
> [...]
Applied, thanks!
[1/4] pveceph: fix Ceph Manager abbreviation
commit: 5ccfb4f7a94e91be4fa41c09a36b1997beaf8e4d
[2/4] pve-storage-cephfs: describe CephFS, not RBD, in external cluster setup
commit: 4f3f7a1038ca24f79c27f8f2b6ee620c6e239dd5
[3/4] pveceph: various small language fixes
commit: 01181b64f43806d3ab5121654393c2d71acf2c44
[4/4] docs: various small grammar fixes
commit: 86e54296fd6684451b2c63d6c76f2e3fa5ba72ad
prev parent reply other threads:[~2026-04-30 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 12:50 [PATCH docs 0/4] ceph: audit of Ceph-related chapters Kefu Chai
2026-04-11 12:50 ` [PATCH docs 1/4] pveceph: fix Ceph Manager abbreviation Kefu Chai
2026-04-11 12:50 ` [PATCH docs 2/4] pve-storage-cephfs: describe CephFS, not RBD, in external cluster setup Kefu Chai
2026-04-11 12:50 ` [PATCH docs 3/4] pveceph: various small language fixes Kefu Chai
2026-04-11 12:50 ` [PATCH docs 4/4] docs: various small grammar fixes Kefu Chai
2026-04-30 11:28 ` 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=177754853204.1242101.10501126077373084159.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=k.chai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.